
From owner-radiusext@ops.ietf.org  Thu Apr  1 17:34: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 461D93A6970 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  1 Apr 2010 17:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.41
X-Spam-Level: **
X-Spam-Status: No, score=2.41 tagged_above=-999 required=5 tests=[AWL=-0.825, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, 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 NdP3M-qImIoz for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  1 Apr 2010 17:34:43 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id A04313A6965 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  1 Apr 2010 17:34:34 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NxUnC-0005Ks-Lq for radiusext-data0@psg.com; Fri, 02 Apr 2010 00:31:22 +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 1NxUn9-0005Kg-Ou for radiusext@ops.ietf.org; Fri, 02 Apr 2010 00:31:19 +0000
Received: from BLU137-DS13 ([65.55.116.9]) by blu0-omc1-s5.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 1 Apr 2010 17:31:18 -0700
X-Originating-IP: [131.107.0.109]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS1300A51C213E6DADCD09DD931C0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: FW: review of draft-ietf-radext-status-server-06.txt
Date: Thu, 1 Apr 2010 17:31:58 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrRqmrNy4lT1majTsu96vl6O371+gAUXYuA
Content-Language: en-us
X-OriginalArrivalTime: 02 Apr 2010 00:31:18.0919 (UTC) FILETIME=[CFF18970:01CAD1FB]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

-----Original Message-----
From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr] 
Sent: Thursday, April 01, 2010 7:48 AM
To: gen-art@ietf.org
Cc: draft-ietf-radext-status-server.all@tools.ietf.org
Subject: review of draft-ietf-radext-status-server-06.txt

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-radext-status-server-06.txt
Reviewer: Francis Dupont
Review Date: 2010-03-28
IETF LC End Date: 2010-03-29
IESG Telechat date: unknown

Summary: Ready with nits

Major issues: none

Minor issues: none

Nits/editorial comments:
 - Abstract page 2: there is an explicit reference to a RFC, this is in
  general forbidden but IMHO we are here in the allowed exception case.

 - 2.1.1 page 8: a servers policy -> a server policy

 - 3 page 10 (twice): etc. -> etc., ???

 - 4.2 page 13: adminstrators -> administrators

 - 4.2 page 15 (twice): e.g. -> e.g.,

 - 4.3 page 16: modelled -> modeled

 - 4.3 page 16: usually the hysteresis against flapping tries to keep
  the connection (i.e., failover after 3 missed responses), here it is
  the opposite. IMHO it is very aggressive but it is how RFC 3539 works
  so I have no concern about it.

 - 4.5 page 16: Proxyhas -> Proxy has

 - 4.5 page 17: cannot, -> cannot

 - 4.5 page 18: i.e. -> i.e.,

 - 5 page 19: EAP-MEssage -> EAP-Message

 - 8 page 23: synthesise -> synthesize

 - 8 page 23: in "the suggestion of [RFC5080] Section 2.2.2, which suggests"
  suggests -> proposes

 - 8 page 23: configurably is not in my dict?

 - 9.2 page 23: IMHO the RFC2119 reference should be moved to normative
  references section (perhaps others too?)

 - Authors' Addresses -> Author's Address

Regards

Francis.Dupont@fdupont.fr

PS: I apologize for the delay. BTW I've seen a wording comment and proposal
from Bernard Aboba, I support it.


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr  6 22:27: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 450C928C10F for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  6 Apr 2010 22:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.574
X-Spam-Level: *
X-Spam-Status: No, score=1.574 tagged_above=-999 required=5 tests=[AWL=-1.132, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_32=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 im2lX00N7JOq for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  6 Apr 2010 22:26:43 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6F7C33A6A80 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue,  6 Apr 2010 22:25:27 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NzNcf-000Kgd-0G for radiusext-data0@psg.com; Wed, 07 Apr 2010 05:16:17 +0000
Received: from [65.55.116.35] (helo=blu0-omc1-s24.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NzNcV-000Kfs-1A for radiusext@ops.ietf.org; Wed, 07 Apr 2010 05:16:07 +0000
Received: from BLU137-DS4 ([65.55.116.7]) by blu0-omc1-s24.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 6 Apr 2010 22:16:06 -0700
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS4558D2B9C8D745F1CDB3B93170@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Draft minutes of IETF 77 RADEXT WG meeting
Date: Tue, 6 Apr 2010 22:16:44 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007E_01CAD5D6.D7C15610"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrWEYOpSdBfdz+kTPe8fOmcntkrKg==
Content-Language: en-us
X-OriginalArrivalTime: 07 Apr 2010 05:16:06.0212 (UTC) FILETIME=[6CD44840:01CAD611]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

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

RADEXT WG Minutes

IETF 77

Anaheim, California USA

Working <http://tools.ietf.org/wg/radext/>  Group Home Page

Jabber room:  radext at jabber.ietf.org

Chairs
        Bernard Aboba <bernard_aboba at hotmail.com
<mailto:bernard_aboba%20at%20hotmail.com> > 
        David Nelson <d.b.nelson at Comcast.net
<mailto:d.b.nelson@comcast.net> >

Agenda
March 22, 2010
 
17:40 - 17:50 PT: Preliminaries 
 
     Bluesheets
     Attendance
     Note takers
     Agenda bash
     Document Status
 
RADEXT WG Agenda Slides
 
Document Status:
 
l  Completed IETF Last Call: Waiting for Revision
l  Design Guidelines <http://tools.ietf.org/html/draft-ietf-radext-design>  
l  In IETF Last Call
l  Status-Server
<http://tools.ietf.org/html/draft-ietf-radext-status-server>  
Comments so far:  An editorial NIT
(http://www.mail-archive.com/ietf@ietf.org/msg45725.html ), and a Gen-Art
review (http://www.ietf.org/mail-archive/web/radext/current/msg01590.html )
l   AD Review: Waiting for Revision 
l  RADIUS over TCP
<http://tools.ietf.org/html/draft-ietf-radext-tcp-transport> 
AD review comments: 
l  Completed RADEXT WG last call: Waiting for PROTO Writeup 
l  New Tunnel Type Values
<http://tools.ietf.org/html/draft-tiwari-radext-tunnel-type>  
l  In RADEXT WG Last Call
l  IPv6 RADIUS attributes
<http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-dhcp-00>  
l  RADIUS over TLS <http://tools.ietf.org/html/draft-ietf-radext-radsec>  
l  RADEXT WG Work Items
l  NAI-based Peer Discovery
<http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery>  
l  RADIUS Crypto-agility Requirements
<http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements>  
l  Extended RADIUS Attributes
<http://tools.ietf.org/html/draft-ietf-radext-extended-attributes>  
l  Under Review as a RADEXT WG Work Item
l  RADIUS Attributes for IEEE 802 Networks
<http://tools.ietf.org/html/draft-aboba-radext-wlan>  
l  RADIUS over DTLS <http://tools.ietf.org/html/draft-dekok-radext-dtls> 
 
 
SECURE RADIUS TRANSPORT (30 minutes)
 
1750 - 1800 AM PT  RTLS, Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec
 
 
RADIUS over TLS Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-2.pdf> 
 
Stefan Winter: We have incorporated proposed resolutions for all open issues
in the tracker within the latest version (-06
<http://tools.ietf.org/html/draft-ietf-radext-radsec-06> ). The document is
ready for another WG last call.
Bernard Aboba: We have started another WG last call (see
http://www.ietf.org/mail-archive/web/radext/current/msg01578.html ).  This
will go until April 19, 2010.  Please read the document and send your review
to the list. 
 
1800 AM - 1810 PT NAI-Based Peer Discovery, Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery
 
 
RADIUS NAI Discovery Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-4.pdf> 
 
Stefan Winter:  Several open issues:
.         S-NAPTR. 
.         Include Diameter?
.         Reference RFC 4282?
.         Guidance on connection attempts (IPv4 vs. IPv6)
 
Alan DeKok:  RFC 4282 is badly broken.  
Bernard Aboba:  Agreed. My advice is to avoid referencing it.  Instead, you
can just reference IDNAbis and tell people to convert U-labels to A-labels
prior to sending DNS queries.  
Hannes Tschofenig: Why are you using S-NAPTR?  Wouldn't it be easier to use
U-NAPTR and a AAA URI?
Stefan Winter:  U-NAPTR might be simpler, if we could utilize the AAA URI
scheme. 
Bernard Aboba: Was Diameter peer discovery ever implemented?
Hannes Tschofenig:  No. 
Bernard Aboba:  Might make sense to explore whether we can come up with a
single solution for Diameter and RADIUS.  Perhaps this should be brought up
in DIME. 
Stefan Winter:  Recommend we stay out of the IPv4 vs. IPv6 issue. 
Bernard Aboba: Big issue so far has been IPv6 blackholing.  Typical causes
are broken tunnels, problems in IPv6 routing, or lack of connectivity
between Teredo/6to4 and native IPv6 Internet.  These problems are more
likely to show up in consumer deployments than in AAA infrastructure.  So it
seems less likely that AAA will need things like DNS IPv6 whitelisting and
perhaps it doesn't matter.  
 
1810 - 1820 PT RADIUS over DTLS, Alan DeKok     (10 minutes)
http://tools.ietf.org/html/draft-dekok-radext-dtls
 
 
RADIUS over DTLS Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-3.ppt> 
 
Alan DeKok:  Major new content in -02. One of the major differences between
RADIUS over TLS and RADIUS over DTLS is that DTLS uses the existing RADIUS
ports.  So you have DTLS and conventional RADIUS being sent to the same port
and the RADIUS implementation has to distinguish DTLS from regular RADIUS
packets.  This is done by looking at the first byte of the RADIUS packet.
If the first byte is 22, then the packet is DTLS, not RADIUS.  For a given 5
tuple (IP Destination address, IP source address, destination port, source
port, UDP), there can only be one choice (DTLS or conventional RADIUS).
This can be implemented on the server in multiple ways.  The server can keep
state in memory relating to whether DTLS or conventional RADIUS was received
on a given 5 tuple.  Or it can keep state in stable storage.  Once DTLS is
received from a given NAS, it can be assumed that the NAS has been upgraded,
and after that, DTLS will always be assumed/required.  The stable storage
approach prevents downgrade attacks after a reboot.
Alan DeKok:  The RADIUS over DTLS document references the RTLS specification
were appropriate, and provides deltas to it.  So the RDTLS document has a
dependency on the RTLS document, but not the other way around.  This makes
since, RADIUS over DTLS implementations are behind RADIUS over TLS by a few
years. 
Stefan Winter: We looked at combining the RADIUS over TLS and RADIUS over
DTLS documents.  However, the documents were at varying levels of maturity
(RTLS has been out for a while, there are multiple interoperable
implementations, DTLS is not yet there), so we didn't think it made sense.
Bernard Aboba: Have there been bakeoffs yet to demonstrate RADIUS over DTLS
interoperability?
Alan DeKok:  Not yet. 
 
 
IPv6 (20 minutes)
 
1820 - 1830  RADIUS Attributes for IPv6 Networks, W. Dec (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-ipv6-access
 
RADIUS Attributes for IPv6 Access Networks Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-6.ppt> 
 
Bernard Aboba:  This document is currently in RADEXT WG last call (see
announcement:
http://www.ietf.org/mail-archive/web/radext/current/msg01547.html  ).  Last
call ended yesterday (March 21, 2010).  However, we only received a few
comments, so will extend last call for a few weeks after IETF 77 to allow
for additional reviews.  Please read the document and send your reviews to
the list, even if it's only to say that the document is fine.  It's not very
long. 
W. Dec:  With early versions of the document, there were concerns about
whether we were trying to create a protocol to handle generic support of
DHCP within RADIUS with no authentication involved.  That is not the
purpose;  we added Section 2 to describe the scenarios. 
 Bernard Aboba:  The protocol exchanges described in the Virtual Interim
(e.g. use of DHCPv6 for configuration and address assignment over PPP
instead of IPv6CP and RA) aren't in Section 2. It would help to refer to
them so that it is clear that authentication is always expected to occur, as
required in RFC 2865.  
W. Dec:  We have received comments in WG last call from Peter Deacon,
relating to existing practices (e.g. how existing implementations use a
combination of Framed-IPv6-Prefix and Framed-Interface-Id to denote an IPv6
address).  The draft describes how a single attribute IPv6-Framed-Address,
can be used in an Accounting-Request, but it doesn't update RFC 3162, so
that attributes allowed in Accounting-Request messages are still legal.  
Alan DeKok:  Shouldn't IPv6-Framed-Address be Framed-IPv6-Address?
 
1830 - 1840  Accounting Extensions for IPv6, R. Maglione (10 minutes)
http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions
 
RADIUS Accounting for IPv6 Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-5.ppt> 
 
There have been a number of review comments on the list. 
>From Avi Lior: http://ops.ietf.org/lists/radiusext/2010/msg00193.html
(Existing attributes are not just for IPv4, they count both IPv4 and IPv6).

Alan DeKok: http://ops.ietf.org/lists/radiusext/2010/msg00220.html (suggest
sending two Accounting-Requests, one for IPv4 and another for IPv6 (using
existing attributes).  Distinguish the accounting streams based on use of
NAS-IP-Address/NAS-IPv6-Address attributes.  Use Acct-Multi-Session-Id used
to link the two streams together.  This approach  seems operationally too
heavy for both the BRAS and the RADIUS system.  Defining new attributes
appears a simpler solution, and doesn't require changing the meaning of
existing attributes (which appear to apply to both IPv4 and IPv6).  
Bernard Aboba:  Changing the meaning of existing accounting attributes based
on the presence of another attribute (NAS-IP-Address/NAS-IPv6-Address) would
represent a "polymorphic attribute" approach, which is discouraged in Design
Guidelines.  The approach of defining new attributes avoid this problem.  
 
Design Guidelines (50 minutes)
 
1840  - 1930  Design Guidelines, Alan DeKok     (50 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines
 
RADIUS Design Guidelines Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-1.ppt> 
 
Alan DeKok:  People have commented on the background of the slides.
Bernard Aboba:  About the flames? 
Alan DeKok:  Yes. 
Bernard Aboba:  Here is where we are on Design Guidelines. With respect to
the Last Look, a summary was sent to the RADEXT WG list on January 28, 2010:
http://www.ietf.org/mail-archive/web/radext/current/msg01472.html
 
As described in the summary, the chairs believe that there is WG consensus
against publication of the Design Guidelines document in its current form.
Therefore, the document cannot be advanced until the issues are addressed. 
 
Three issues were opened against the document as a result of the "Last
Look".  One issue was opened by Hannes Tschofenig, relating to the
organization of the document (see
http://www.ietf.org/mail-archive/web/radext/current/msg01515.html ).  
Alan DeKok:  I believe that this issue is resolved in -12
<http://tools.ietf.org/html/draft-ietf-radext-design> . 
 
Another is Issue 325 (opened by Joe Salowey), which relates to the text on
complex attributes.  The issues relates to problems with both the statements
of fact (relating to whether code changes are required in certain
situations) as well as the recommendations.   Changes were made in -11 and
-12 to resolve this issue. Joe has indicated that the suggested changes were
helpful (see
http://www.ietf.org/mail-archive/web/radext/current/msg01434.html), so I am
going to close the issue. 
 
Since other "Last Look" comments appear to indicate that the changes are
insufficient, it is possible that there are additional changes required, but
we don't have specific comments or text changes on the table. How do we move
forward? 
Alan DeKok: I will solicit feedback on the list (done, see
http://www.ietf.org/mail-archive/web/radext/current/msg01588.html ). 
Bernard Aboba:  If you have concerns relating to the text on complex
attributes, please submit specific changes to the list.  The time for
general comments is past. This document has completed WG last call and IETF
last call and IESG DISCUSS comments have been resolved.  We need text to
move forward.  
 
On Issue 327 (opened as a result of postings by Avi Lior), a proposal for
resolution was made and discussed at the Virtual Interim (see
http://www.ietf.org/mail-archive/web/radext/current/msg01496.html )  Avi
accepted the resolution, but the suggested resolution has not yet been
reflected in the document. 
Alan DeKok:  In -12 I focused on improving document readability.  Since
there were so many editorial changes to the document, the proposal no longer
applied.
Bernard Aboba:  I will take an action item to resubmit the proposed
resolution, based on the -12 organization.  However, I do not believe that
Issue 327 has been resolved, so I will not close it. 
 
Wrap-up (10 minutes)
 
1930 - 1940  Discussion and Next Steps:  WG Chairs & ADs (10 minutes)

 


------=_NextPart_000_007E_01CAD5D6.D7C15610
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Times;
	panose-1:2 2 6 3 5 4 5 2 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	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.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";}
.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;}
 /* List Definitions */
 @list l0
	{mso-list-id:547448458;
	mso-list-type:hybrid;
	mso-list-template-ids:791336830 -1792493236 267138734 -55679474 =
-1271366590 -2118354756 801817786 -1204915546 -1132534694 -627147322;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F06C;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level2
	{mso-level-start-at:887;
	mso-level-number-format:bullet;
	mso-level-text:\F06C;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level3
	{mso-level-start-at:887;
	mso-level-number-format:bullet;
	mso-level-text:\F06C;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1168910503;
	mso-list-type:hybrid;
	mso-list-template-ids:-1264437688 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</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'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal'><b><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>RADEXT
WG Minutes</span></b><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;
line-height:normal'><b><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>IETF
77</span></b><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;
line-height:normal'><b><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Anaheim,
California USA</span></b><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;margin-bottom:12.0pt;
line-height:normal'><a name=3Dwg-martini></a><span =
style=3D'font-size:10.0pt;
font-family:"Times","serif"'><a =
href=3D"http://tools.ietf.org/wg/radext/">Working
Group Home Page</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;margin-bottom:12.0pt;
line-height:normal'><span =
style=3D'font-size:10.0pt;font-family:"Times","serif"'>Jabber
room:&nbsp; radext at jabber.ietf.org<br>
<br>
Chairs<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Bernard Aboba &lt;<a
href=3D"mailto:bernard_aboba%20at%20hotmail.com">bernard_aboba at =
hotmail.com</a>&gt;
<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; David Nelson &lt;<a
href=3D"mailto:d.b.nelson@comcast.net">d.b.nelson at =
Comcast.net</a>&gt;</span><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<pre>Agenda<o:p></o:p></pre><pre>March 22, =
2010<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>17:40 &#8211; =
17:50 PT: Preliminaries =
<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp=
; Bluesheets<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp; =
Attendance<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp; Note =
takers<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp; Agenda =
bash<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp; Document =
Status<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><u><span
style=3D'font-family:"Arial","sans-serif";color:blue'>RADEXT WG Agenda =
Slides</span></u><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Docume=
nt Status:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>Completed IETF Last Call: Waiting for =
Revision<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design">Design =
Guidelines</a> <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>In IETF Last Call<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">Statu=
s-Server</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in'>Comments so far:&nbsp; An editorial NIT (<a
href=3D"http://www.mail-archive.com/ietf@ietf.org/msg45725.html">http://w=
ww.mail-archive.com/ietf@ietf.org/msg45725.html</a> ), and a Gen-Art =
review (<a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01590.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01590.html</a> =
)<o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>&nbsp;AD Review: Waiting for Revision =
<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport">RADIU=
S over TCP</a><o:p></o:p></pre><pre
style=3D'margin-left:1.0in'>AD review comments: <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>Completed RADEXT WG last call: Waiting =
for PROTO Writeup <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-tiwari-radext-tunnel-type">New =
Tunnel Type Values</a> <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>In RADEXT WG Last =
Call<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-dhcp-00">I=
Pv6 RADIUS attributes</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">RADIUS over =
TLS</a> <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>RADEXT WG Work Items<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">N=
AI-based Peer Discovery</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requi=
rements">RADIUS Crypto-agility Requirements</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-extended-attributes"=
>Extended RADIUS Attributes</a> <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>Under Review as a RADEXT WG Work =
Item<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-aboba-radext-wlan">RADIUS =
Attributes for IEEE 802 Networks</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-dekok-radext-dtls">RADIUS over =
DTLS</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:=
p></pre><pre>SECURE RADIUS TRANSPORT (30 =
minutes)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1750 &#8211; =
1800 AM PT&nbsp; RTLS, Stefan Winter (10 =
minutes)<o:p></o:p></pre><pre><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></pre><pre><o:p>&nb=
sp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-2.pdf">RADIUS=
 over TLS Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre>Stefan Winter: We have incorporated proposed resolutions for all =
open issues in the tracker within the latest version (<a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec-06">-06</a>).=
 The document is ready for another WG last =
call.<o:p></o:p></pre><pre>Bernard Aboba: We have started another WG =
last call (see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01578.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01578.html</a> =
).&nbsp; This will go until April 19, 2010.&nbsp; Please read the =
document and send your review to the list. =
<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>1800 AM - 1810 PT =
NAI-Based Peer Discovery, Stefan Winter (10 =
minutes)<o:p></o:p></pre><pre><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></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><sp=
an
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-4.pdf">RADIUS=
 NAI Discovery Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre>Stefan Winter:&nbsp; Several open issues:<o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>S-NAPTR. <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Include Diameter?<o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Reference RFC 4282?<o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Guidance on connection attempts (IPv4 vs. =
IPv6)<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Alan DeKok:&nbsp; =
RFC 4282 is badly broken.&nbsp; <o:p></o:p></pre><pre>Bernard =
Aboba:&nbsp; Agreed. My advice is to avoid referencing it.&nbsp; =
Instead, you can just reference IDNAbis and tell people to convert =
U-labels to A-labels prior to sending DNS queries.&nbsp; =
<o:p></o:p></pre><pre>Hannes Tschofenig: Why are you using =
S-NAPTR?&nbsp; Wouldn&#8217;t it be easier to use U-NAPTR and a AAA =
URI?<o:p></o:p></pre><pre>Stefan Winter:&nbsp; U-NAPTR might be simpler, =
if we could utilize the AAA URI scheme. <o:p></o:p></pre><pre>Bernard =
Aboba: Was Diameter peer discovery ever =
implemented?<o:p></o:p></pre><pre>Hannes Tschofenig:&nbsp; No. =
<o:p></o:p></pre><pre>Bernard Aboba:&nbsp; Might make sense to explore =
whether we can come up with a single solution for Diameter and =
RADIUS.&nbsp; Perhaps this should be brought up in DIME. =
<o:p></o:p></pre><pre>Stefan Winter:&nbsp; Recommend we stay out of the =
IPv4 vs. IPv6 issue. <o:p></o:p></pre><pre>Bernard Aboba: Big issue so =
far has been IPv6 blackholing.&nbsp; Typical causes are broken tunnels, =
problems in IPv6 routing, or lack of connectivity between Teredo/6to4 =
and native IPv6 Internet.&nbsp; These problems are more likely to show =
up in consumer deployments than in AAA infrastructure.&nbsp; So it seems =
less likely that AAA will need things like DNS IPv6 whitelisting and =
perhaps it doesn&#8217;t matter.&nbsp; =
<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1810 &#8211; 1820 PT =
RADIUS over DTLS, Alan DeKok&nbsp;&nbsp;&nbsp;&nbsp; (10 =
minutes)<o:p></o:p></pre><pre><a
href=3D"http://tools.ietf.org/html/draft-dekok-radext-dtls">http://tools.=
ietf.org/html/draft-dekok-radext-dtls</a><o:p></o:p></pre><pre><o:p>&nbsp=
;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-3.ppt">RADIUS=
 over DTLS Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre>Alan DeKok:&nbsp; Major new content in -02. One of the major =
differences between RADIUS over TLS and RADIUS over DTLS is that DTLS =
uses the existing RADIUS ports.&nbsp; So you have DTLS and conventional =
RADIUS being sent to the same port and the RADIUS implementation has to =
distinguish DTLS from regular RADIUS packets.&nbsp; This is done by =
looking at the first byte of the RADIUS packet.&nbsp; If the first byte =
is 22, then the packet is DTLS, not RADIUS.&nbsp; For a given 5 tuple =
(IP Destination address, IP source address, destination port, source =
port, UDP), there can only be one choice (DTLS or conventional =
RADIUS).&nbsp; This can be implemented on the server in multiple =
ways.&nbsp; The server can keep state in memory relating to whether DTLS =
or conventional RADIUS was received on a given 5 tuple.&nbsp; Or it can =
keep state in stable storage.&nbsp; Once DTLS is received from a given =
NAS, it can be assumed that the NAS has been upgraded, and after that, =
DTLS will always be assumed/required.&nbsp; The stable storage approach =
prevents downgrade attacks after a reboot.<o:p></o:p></pre><pre>Alan =
DeKok:&nbsp; The RADIUS over DTLS document references the RTLS =
specification were appropriate, and provides deltas to it.&nbsp; So the =
RDTLS document has a dependency on the RTLS document, but not the other =
way around.&nbsp; This makes since, RADIUS over DTLS implementations are =
behind RADIUS over TLS by a few years. <o:p></o:p></pre><pre>Stefan =
Winter: We looked at combining the RADIUS over TLS and RADIUS over DTLS =
documents.&nbsp; However, the documents were at varying levels of =
maturity (RTLS has been out for a while, there are multiple =
interoperable implementations, DTLS is not yet there), so we =
didn&#8217;t think it made sense.<o:p></o:p></pre><pre>Bernard Aboba: =
Have there been bakeoffs yet to demonstrate RADIUS over DTLS =
interoperability?<o:p></o:p></pre><pre>Alan DeKok:&nbsp; Not yet. =
<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp;<o:p></o:p></pre>=
<pre>IPv6 (20 =
minutes)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1820 &#8211; =
1830 &nbsp;RADIUS Attributes for IPv6 Networks, W. Dec (10 =
minutes)<o:p></o:p></pre><pre><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-ipv6-access">http://=
tools.ietf.org/html/draft-ietf-radext-ipv6-access</a><o:p></o:p></pre><pr=
e><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-6.ppt">RADIUS=
 Attributes for IPv6 Access Networks =
Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; This =
document is currently in RADEXT WG last call (see announcement:</span> =
<span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01547.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01547.html</a>&n=
bsp; ).&nbsp; Last call ended yesterday (March 21, 2010).&nbsp; However, =
we only received a few comments, so will extend last call for a few =
weeks after IETF 77 to allow for additional reviews.&nbsp; Please read =
the document and send your reviews to the list, even if it&#8217;s only =
to say that the document is fine.&nbsp; It&#8217;s not very long. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>W. Dec:&nbsp; With early =
versions of the document, there were concerns about whether we were =
trying to create a protocol to handle generic support of DHCP within =
RADIUS with no authentication involved.&nbsp; That is not the =
purpose;&nbsp; we added Section 2 to describe the scenarios. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>&nbsp;Bernard Aboba:&nbsp; =
The protocol exchanges described in the Virtual Interim (e.g. use of =
DHCPv6 for configuration and address assignment over PPP instead of =
IPv6CP and RA) aren&#8217;t in Section 2. It would help to refer to them =
so that it is clear that authentication is always expected to occur, as =
required in RFC 2865.&nbsp; <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>W. Dec:&nbsp; We have =
received comments in WG last call from Peter Deacon, relating to =
existing practices (e.g. how existing implementations use a combination =
of Framed-IPv6-Prefix and Framed-Interface-Id to denote an IPv6 =
address).&nbsp; The draft describes how a single attribute =
IPv6-Framed-Address, can be used in an Accounting-Request, but it =
doesn&#8217;t update RFC 3162, so that attributes allowed in =
Accounting-Request messages are still legal.&nbsp; =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; =
Shouldn&#8217;t IPv6-Framed-Address be =
Framed-IPv6-Address?<o:p></o:p></span></pre><pre>&nbsp;<o:p></o:p></pre><=
pre>1830 - 1840 &nbsp;Accounting Extensions for IPv6, R. Maglione (10 =
minutes)<o:p></o:p></pre><pre><a
href=3D"http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extens=
ions">http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensio=
ns</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-5.ppt">RADIUS=
 Accounting for IPv6 Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>There have been =
a number of review comments on the list. =
<o:p></o:p></span></pre><pre><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>From Avi Lior: =
<a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00193.html">http://op=
s.ietf.org/lists/radiusext/2010/msg00193.html</a>&nbsp; (Existing =
attributes are not just for IPv4, they count both IPv4 and IPv6).&nbsp; =
<o:p></o:p></span></pre><pre><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>Alan DeKok: <a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00220.html">http://op=
s.ietf.org/lists/radiusext/2010/msg00220.html</a> (suggest sending two =
Accounting-Requests, one for IPv4 and another for IPv6 (using existing =
attributes).&nbsp; Distinguish the accounting streams based on use of =
NAS-IP-Address/NAS-IPv6-Address attributes.&nbsp; Use </span><i><span
style=3D'font-family:"Arial","sans-serif"'>Acct-Multi-Session-Id =
</span></i><span
style=3D'font-family:"Arial","sans-serif"'>used to link the two streams =
together.&nbsp; </span><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>This =
approach&nbsp; seems operationally too heavy for both the BRAS and the =
RADIUS system.&nbsp; Defining new attributes appears a simpler solution, =
and doesn&#8217;t require changing the meaning of existing attributes =
(which appear to apply to both IPv4 and IPv6).&nbsp; =
<o:p></o:p></span></pre><pre><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>Bernard =
Aboba:&nbsp; Changing the meaning of existing accounting attributes =
based on the presence of another attribute =
(NAS-IP-Address/NAS-IPv6-Address) would represent a &#8220;polymorphic =
attribute&#8221; approach, which is discouraged in Design =
Guidelines.&nbsp; The approach of defining new attributes avoid this =
problem.&nbsp; =
<o:p></o:p></span></pre><pre>&nbsp;<o:p></o:p></pre><pre>Design =
Guidelines (50 =
minutes)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1840 =
&nbsp;&#8211; 1930 &nbsp;Design Guidelines, Alan =
DeKok&nbsp;&nbsp;&nbsp;&nbsp; (50 minutes)<o:p></o:p></pre><pre><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></pre><pre><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-1.ppt">RADIUS=
 Design Guidelines Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; People have =
commented on the background of the =
slides&#8230;<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; About =
the flames? <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; Yes. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; Here is =
where we are on Design Guidelines. With respect to the Last Look, a =
summary was sent to the RADEXT WG list on January 28, =
2010:<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01472.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01472.html</a><o=
:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>As described in the summary, =
the chairs believe that there is WG consensus against publication of the =
Design Guidelines document in its current form.&nbsp; Therefore, the =
document cannot be advanced until the issues are addressed. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Three issues were opened =
against the document as a result of the &#8220;Last Look&#8221;.&nbsp; =
One issue was opened by Hannes Tschofenig, relating to the organization =
of the document (see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01515.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01515.html</a> =
).&nbsp; <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; I believe =
that this issue is resolved in <a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design">-12</a>. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Another is Issue 325 (opened =
by Joe Salowey), which relates to the text on complex attributes.&nbsp; =
The issues relates to problems with both the statements of fact =
(relating to whether code changes are required in certain situations) as =
well as the recommendations.&nbsp;&nbsp; Changes were made in -11 and =
-12 to resolve this issue. Joe has indicated that the suggested changes =
were helpful (see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01434.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01434.html</a>),=
 so I am going to close the issue. <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Since other &#8220;Last =
Look&#8221; comments appear to indicate that the changes are =
insufficient, it is possible that there are additional changes required, =
but we don&#8217;t have specific comments or text changes on the table. =
How do we move forward? <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok: I will solicit =
feedback on the list (done, see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01588.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01588.html</a> =
). <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; If you =
have concerns relating to the text on complex attributes, please submit =
specific changes to the list.&nbsp; The time for general comments is =
past. This document has completed WG last call and IETF last call and =
IESG DISCUSS comments have been resolved.&nbsp; We need text to move =
forward.&nbsp; <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>On Issue 327 (opened as a =
result of postings by Avi Lior), a proposal for resolution was made and =
discussed at the Virtual Interim (see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01496.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01496.html</a> =
)&nbsp; Avi accepted the resolution, but the suggested resolution has =
not yet been reflected in the document. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; In -12 I =
focused on improving document readability.&nbsp; Since there were so =
many editorial changes to the document, the proposal no longer =
applied.<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; I will =
take an action item to resubmit the proposed resolution, based on the =
-12 organization.&nbsp; However, I do not believe that Issue 327 has =
been resolved, so I will not close it. =
<o:p></o:p></span></pre><pre>&nbsp;<o:p></o:p></pre><pre>Wrap-up (10 =
minutes)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1930 - 1940 =
&nbsp;Discussion and Next Steps:&nbsp; WG Chairs &amp; ADs (10 =
minutes)<o:p></o:p></pre>

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

</div>

</body>

</html>

------=_NextPart_000_007E_01CAD5D6.D7C15610--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 13 08:01: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 E43723A6A3F for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 13 Apr 2010 08:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id haqVsCeRus1m for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 13 Apr 2010 08:01:20 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 9F4B93A6A4E for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 13 Apr 2010 08:01:17 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O1hYS-0006ey-DX for radiusext-data0@psg.com; Tue, 13 Apr 2010 14:57: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 1O1hYQ-0006eZ-1R for radiusext@ops.ietf.org; Tue, 13 Apr 2010 14:57:30 +0000
Message-ID: <4BC48655.4070504@deployingradius.com>
Date: Tue, 13 Apr 2010 16:57:25 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: (repost) Reminder for review of Design Guidelines document
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

  We've had one review so far.  More would be better.

  The guidelines document was updated significantly to address the open
concerns.  The latest revision is available at:

http://tools.ietf.org/html/draft-ietf-radext-design-12

  The high-level differences are an update as per the review from
Hannes.  The outline is now:

introduction	(2 pages)
guidelines	(3 pages)
rationale	(11 pages)

  The "guidelines" section gives the guidelines with no supporting
arguments.  All of the arguments are in the "rationale" section.  We
hope that this organization makes the guidelines easier to understand.

  The document still needs some minor editing, and also should integrate
comments from Issue #327.  However, these changes are expected to be
minor, and we are looking for feedback on the current draft.

  A diff is at:

http://tools.ietf.org/rfcdiff?url2=draft-ietf-radext-design-12.txt

  The diff isn't that useful, as too much has changed.

  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 Apr 13 12:46:36 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 332D528C157 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 13 Apr 2010 12:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.135
X-Spam-Level: *
X-Spam-Status: No, score=1.135 tagged_above=-999 required=5 tests=[AWL=-0.785, 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 jr7FBEiJSZlz for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 13 Apr 2010 12:46:35 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id A8FC528C118 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 13 Apr 2010 12:46:34 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O1m0T-0001FG-MD for radiusext-data0@psg.com; Tue, 13 Apr 2010 19:42:45 +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 1O1m0Q-0001C1-E7 for radiusext@ops.ietf.org; Tue, 13 Apr 2010 19:42:42 +0000
Received: from BLU137-W23 ([65.55.116.9]) by blu0-omc1-s28.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 13 Apr 2010 12:42:08 -0700
Message-ID: <BLU137-W2335B6060EFAF690A6342093110@phx.gbl>
Content-Type: multipart/alternative; boundary="_0b59c8f2-c3c8-4fd3-9891-257bafc3ef2a_"
X-Originating-IP: [24.19.160.219]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RE: (repost) Reminder for review of Design Guidelines document
Date: Tue, 13 Apr 2010 12:42:08 -0700
Importance: Normal
In-Reply-To: <4BC48655.4070504@deployingradius.com>
References: <4BC48655.4070504@deployingradius.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Apr 2010 19:42:08.0459 (UTC) FILETIME=[673871B0:01CADB41]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_0b59c8f2-c3c8-4fd3-9891-257bafc3ef2a_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


The changes made in -12 largely relate to the organizational issues brought=
 up by Hannes.=20

Therefore it would appear that Issue 327 remains open=2C and possibly some =
of the concerns expressed by Avi and others relating to Issue 325.=20

As a result=2C it would appear that there is still WG consensus against pub=
lication of the document.=20

> Date: Tue=2C 13 Apr 2010 16:57:25 +0200
> From: aland@deployingradius.com
> To: radiusext@ops.ietf.org
> Subject: (repost) Reminder for review of Design Guidelines document
>=20
>   We've had one review so far.  More would be better.
>=20
>   The guidelines document was updated significantly to address the open
> concerns.  The latest revision is available at:
>=20
> http://tools.ietf.org/html/draft-ietf-radext-design-12
>=20
>   The high-level differences are an update as per the review from
> Hannes.  The outline is now:
>=20
> introduction	(2 pages)
> guidelines	(3 pages)
> rationale	(11 pages)
>=20
>   The "guidelines" section gives the guidelines with no supporting
> arguments.  All of the arguments are in the "rationale" section.  We
> hope that this organization makes the guidelines easier to understand.
>=20
>   The document still needs some minor editing=2C and also should integrat=
e
> comments from Issue #327.  However=2C these changes are expected to be
> minor=2C and we are looking for feedback on the current draft.
>=20
>   A diff is at:
>=20
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-radext-design-12.txt
>=20
>   The diff isn't that useful=2C as too much has changed.
>=20
>   Alan DeKok.
>=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/>
 		 	   		  =

--_0b59c8f2-c3c8-4fd3-9891-257bafc3ef2a_
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 changes made in -12 largely relate to the organizational issues brought=
 up by Hannes. <br><br>Therefore it would appear that Issue 327 remains ope=
n=2C and possibly some of the concerns expressed by Avi and others relating=
 to Issue 325. <br><br>As a result=2C it would appear that there is still W=
G consensus against publication of the document. <br><br>&gt=3B Date: Tue=
=2C 13 Apr 2010 16:57:25 +0200<br>&gt=3B From: aland@deployingradius.com<br=
>&gt=3B To: radiusext@ops.ietf.org<br>&gt=3B Subject: (repost) Reminder for=
 review of Design Guidelines document<br>&gt=3B <br>&gt=3B   We've had one =
review so far.  More would be better.<br>&gt=3B <br>&gt=3B   The guidelines=
 document was updated significantly to address the open<br>&gt=3B concerns.=
  The latest revision is available at:<br>&gt=3B <br>&gt=3B http://tools.ie=
tf.org/html/draft-ietf-radext-design-12<br>&gt=3B <br>&gt=3B   The high-lev=
el differences are an update as per the review from<br>&gt=3B Hannes.  The =
outline is now:<br>&gt=3B <br>&gt=3B introduction	(2 pages)<br>&gt=3B guide=
lines	(3 pages)<br>&gt=3B rationale	(11 pages)<br>&gt=3B <br>&gt=3B   The "=
guidelines" section gives the guidelines with no supporting<br>&gt=3B argum=
ents.  All of the arguments are in the "rationale" section.  We<br>&gt=3B h=
ope that this organization makes the guidelines easier to understand.<br>&g=
t=3B <br>&gt=3B   The document still needs some minor editing=2C and also s=
hould integrate<br>&gt=3B comments from Issue #327.  However=2C these chang=
es are expected to be<br>&gt=3B minor=2C and we are looking for feedback on=
 the current draft.<br>&gt=3B <br>&gt=3B   A diff is at:<br>&gt=3B <br>&gt=
=3B http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-radext-design-12.txt<br=
>&gt=3B <br>&gt=3B   The diff isn't that useful=2C as too much has changed.=
<br>&gt=3B <br>&gt=3B   Alan DeKok.<br>&gt=3B <br>&gt=3B <br>&gt=3B --<br>&=
gt=3B to unsubscribe send a message to radiusext-request@ops.ietf.org with<=
br>&gt=3B the word 'unsubscribe' in a single line as the message text body.=
<br>&gt=3B archive: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br> 		 	   =
		  </body>
</html>=

--_0b59c8f2-c3c8-4fd3-9891-257bafc3ef2a_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 13 13:45: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 DA2EC3A6A86 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 13 Apr 2010 13:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.805
X-Spam-Level: 
X-Spam-Status: No, score=0.805 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2CEnRKgWl2Gr for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 13 Apr 2010 13:45:40 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1BAA93A68EE for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 13 Apr 2010 13:45:39 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O1mvw-000Bcu-GM for radiusext-data0@psg.com; Tue, 13 Apr 2010 20:42:08 +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 1O1mvt-000BcY-Dc for radiusext@ops.ietf.org; Tue, 13 Apr 2010 20:42:05 +0000
Message-ID: <4BC4D71C.3050903@deployingradius.com>
Date: Tue, 13 Apr 2010 22:42:04 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: (repost) Reminder for review of Design Guidelines document
References: <4BC48655.4070504@deployingradius.com> <BLU137-W2335B6060EFAF690A6342093110@phx.gbl>
In-Reply-To: <BLU137-W2335B6060EFAF690A6342093110@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:
> The changes made in -12 largely relate to the organizational issues
> brought up by Hannes.

  And others.

> Therefore it would appear that Issue 327 remains open, and possibly some
> of the concerns expressed by Avi and others relating to Issue 325.

  Issue #325 has been addressed in -12.  Issue #327 is being worked on.
 All other concerns are either addressed in -12, or are out of scope of
the document.

> As a result, it would appear that there is still WG consensus against
> publication of the document.

  Given the volume of criticism directed against the document, and the
strong desire that it be re-organized, I would hope that people care
enough to review the -12 version, which directly addresses their
concerns.  If their concerns aren't strong enough to warrant a review of
-12, then I suggest that the concerns aren't serious.

  I will review the text suggested in issue #327 for inclusion in the
next rev of the document.  But the document has changed substantially
since the review was made, and portions of the suggestions are no longer
relevant.

  If there are no other concerns with -12, then I suggest that we do a
-13 addressing issue #327, and call the document "finished".

  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 Apr 14 05:27: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 A32093A6926 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 14 Apr 2010 05:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.246
X-Spam-Level: 
X-Spam-Status: No, score=-102.246 tagged_above=-999 required=5 tests=[AWL=0.354, 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 7emRPh7peqFz for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 14 Apr 2010 05:27:35 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id D15CB3A6BBC for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 14 Apr 2010 05:20:55 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O21Ul-0006zS-KB for radiusext-data0@psg.com; Wed, 14 Apr 2010 12:15:03 +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 1O21Uj-0006yp-4Q for radiusext@ops.ietf.org; Wed, 14 Apr 2010 12:15:01 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id 8200128C281; Wed, 14 Apr 2010 05:15:03 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-design-13.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100414121503.8200128C281@core3.amsl.com>
Date: Wed, 14 Apr 2010 05:15:03 -0700 (PDT)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : RADIUS Design Guidelines
	Author(s)       : G. Weber, A. DeKok
	Filename        : draft-ietf-radext-design-13.txt
	Pages           : 40
	Date            : 2010-04-14

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

Content-Type: text/plain
Content-ID:     <2010-04-14050415.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  Wed Apr 14 05:35: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 3E2E728C202 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 14 Apr 2010 05:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.155
X-Spam-Level: 
X-Spam-Status: No, score=0.155 tagged_above=-999 required=5 tests=[AWL=0.650, 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 PxoFqsQDxnIQ for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 14 Apr 2010 05:35:47 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 79B533A6BC4 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 14 Apr 2010 05:28:57 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O21fO-0009Od-Kb for radiusext-data0@psg.com; Wed, 14 Apr 2010 12:26: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 1O21fJ-0009Nr-Ax for radiusext@ops.ietf.org; Wed, 14 Apr 2010 12:25:57 +0000
Message-ID: <4BC5B453.2010802@deployingradius.com>
Date: Wed, 14 Apr 2010 14:25:55 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Proposal for resolution of Issue 327:  Applicability
References: <BLU137-DS3D85750A8B968C9620D0F934B0@phx.gbl> <BLU137-W377F2298AEEB878B736E09934B0@phx.gbl>
In-Reply-To: <BLU137-W377F2298AEEB878B736E09934B0@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] Proposed change is to replace Section 1 with the following:
> 
>    "This document provides guidelines for the design of RADIUS attributes
>    used to encode service-provisioning or authentication data,
>    based on the data model and attribute formats defined in RFC 2865 and
>    subsequent RADIUS RFCs.

  I think that text is better left in the "Applicability" section.  The
introduction should motivate the document, rather than explaining where
it applies.

>   In order to characterize current attribute
>    usage, both the basic and complex data types defined in the existing 
>    RADIUS RFCs are reviewed. Since the RADEXT WG is currently considering
>    extensions to the RADIUS data model and attribute formats,
>    future documents may extend the data model and guidelines provided here.

  The IETF process already allows for future documents.  I'm not sure
that we need to re-state it here.

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

  The current text in the "Applicability" section motivates the
document, rather than explaining the applicability.

  I suggest starting Section 1.3 with a clear statement of
applicability, using the text suggested above.

  I've addressed the rest of the review in -13 (to be submitted
shortly).  Some of the suggestions didn't apply to -12, and some were
added with re-arrangements.

  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 Apr 14 06:00: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 C59533A698F for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 14 Apr 2010 06:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.062
X-Spam-Level: 
X-Spam-Status: No, score=-0.062 tagged_above=-999 required=5 tests=[AWL=0.433, 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 YtBEg7PfUu6k for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 14 Apr 2010 06:00:47 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0F3643A69A9 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 14 Apr 2010 06:00:01 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O227B-000GEP-Ba for radiusext-data0@psg.com; Wed, 14 Apr 2010 12:54:45 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1O2277-000GBy-NS for radiusext@ops.ietf.org; Wed, 14 Apr 2010 12:54:41 +0000
Message-ID: <4BC5BB10.4080006@deployingradius.com>
Date: Wed, 14 Apr 2010 14:54:40 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: I-D Action:draft-ietf-radext-design-13.txt
References: <20100414121503.8200128C281@core3.amsl.com>
In-Reply-To: <20100414121503.8200128C281@core3.amsl.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>

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the RADIUS EXTensions Working Group of the IETF.
> 
> 
> 	Title           : RADIUS Design Guidelines
> 	Author(s)       : G. Weber, A. DeKok
> 	Filename        : draft-ietf-radext-design-13.txt
> 	Pages           : 40
> 	Date            : 2010-04-14

  See also the 'diff' available at:

http://tools.ietf.org/rfcdiff?url2=draft-ietf-radext-design-13.txt

  This revision incorporates suggestions from all open issues, including
#327.

  Please provide feedback.

  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 Apr 15 09:11: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 E3C903A69A6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 15 Apr 2010 09:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.251
X-Spam-Level: *
X-Spam-Status: No, score=1.251 tagged_above=-999 required=5 tests=[AWL=-0.855, 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 RLDlmylsgwsJ for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 15 Apr 2010 09:11:41 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 93C013A69B9 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 15 Apr 2010 09:11:39 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O2RaK-000Mwk-J3 for radiusext-data0@psg.com; Thu, 15 Apr 2010 16:06:32 +0000
Received: from [65.55.111.86] (helo=blu0-omc2-s11.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1O2RaF-000MwI-R6 for radiusext@ops.ietf.org; Thu, 15 Apr 2010 16:06:28 +0000
Received: from BLU137-W32 ([65.55.111.73]) by blu0-omc2-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 15 Apr 2010 09:06:26 -0700
Message-ID: <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl>
Content-Type: multipart/alternative; boundary="_1de28bcc-3e9d-4f65-87b0-855562c143b3_"
X-Originating-IP: [24.19.160.219]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Alan DeKok <aland@deployingradius.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RE: I-D Action:draft-ietf-radext-design-13.txt
Date: Thu, 15 Apr 2010 09:06:26 -0700
Importance: Normal
In-Reply-To: <0b1001cadbf4$6631bfc0$32953f40$@com>
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com>
MIME-Version: 1.0
X-OriginalArrivalTime: 15 Apr 2010 16:06:26.0823 (UTC) FILETIME=[9A3B0170:01CADCB5]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_1de28bcc-3e9d-4f65-87b0-855562c143b3_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Glancing at -13=2C there appear to be some inconsistencies within the text:

Section 1.3.1

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.

It is RECOMMENDED that SDOs follow the guidelines articulated in this
document. 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 new attributes defined in those
specifications are VSAs. See Section 3=2C below=2C for additional
discussion of this topic.

It is RECOMMENDED that SDOs and vendors seek review of RADIUS
attribute specifications from the IETF. However=2C specifications do
not require IETF review when they satisfy all of the following
criteria:

* are SDO specific=3B

* reference attributes from pre-existing IETF or SDO
specifications=3B

* define new attributes only in the VSA space=3B

* use only the "basic data types" (see below) for all VSAs=3B

* follow the guidelines given in this document.

[BA] This text is similar to text in Section 3.3.3=2C which leads me to
believe that there was an editing problem.
My suggestion is that the text in 3.3.3 be moved to Section 1.3.1.

3.3.3. SDO Allocations

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. Is is therefore RECOMMENDED
that SDO RADIUS Attribute specifications 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:

* attributes relying on data types not defined within RADIUS

* attributes intended primarily for use within an SDO

* attributes intended primarily for use within a group of SDOs.

Any 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].

The recommendation for SDOs to allocate attributes from a vendor
space rather than via the IETF process is a recognition that SDOs
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. The SDO can then allocate
attributes within the VSA space defined by that Vendor-Id=2C at their
sole discretion. Similarly=2C the use of data types (complex or
otherwise) within that VSA space is solely under the discretion of
the SDO.

Nevertheless=2C following the guidelines outlined within this document
has many advantages. It is therefore RECOMMENDED that SDOs follow
the guidelines outlined here=2C which are intended to enable maximum
interoperability with minimal changes to existing systems.

[BA] The last paragraph does not appear to be consistent with Section 1.3=
=2C
so I'd
recommend that it be deleted.

3.3.2. Vendor Allocations

Nevertheless=2C following the guidelines outlined within this document
has many advantages. It is therefore RECOMMENDED that vendors follow
the guidelines outlined here=2C which are intended to enable maximum
interoperability with minimal changes to existing systems. If these
guidelines are not followed=2C the result will be increased complexity
with little or no benefit.

[BA] The resolution to Issue 327 recommended the following alternative text=
:

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
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."

3.3.4. Publication of specifications

In order to enable IETF review of SDO specifications=2C it is
RECOMMENDED that:

* SDOs make their RADIUS attribute specifications publicly
available=3B

* SDOs request review of RADIUS attribute specifications by
sending email to the AAA Doctors [DOCTORS] or equivalent mailing
list=3B

* IETF and SDO RADIUS attribute specifications are reviewed
according to the guidelines proposed in this document=3B

* 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.

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.

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.

SDOs are encouraged to seek early review of their specifications by
the IETF. It should be understood that reviews are a voluntary-based
service offered on best-effort basis.

Where the RADIUS 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.

Similarly=2C vendors are encouraged to make their specifications
publicly available=2C for maximum interoperability. However=2C it is not
necessary for them to request publication of their VSA specifications
as Informational RFCs by the IETF.

All other specifications=2C including new authentication=2C
authorization=2C and/or security mechanisms SHOULD follow the
allocation process defined in [RFC3575].

[BA] The resolution to Issue 327 recommended the following alternative text=
:

SDOs or vendors desiring review of their RADIUS specifications
by the IETF are encouraged to seek review as early as possible=2C
so as to avoid potential delays. Since reviews are handled by volunteers=2C
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
an Informational RFC=2C as with [RFC4679].

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.

The review process requires neither allocation of attributes
within the IETF standard attribute space nor publication of an
IETF RFC. Requiring SDOs or vendors to rehost VSAs into the IETF standards
attribute space solely for the purpose of obtaining review
would put pressure on the standards space=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."

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] =
On
> Behalf Of Alan DeKok
> Sent: Wednesday=2C April 14=2C 2010 5:55 AM
> To: radiusext@ops.ietf.org
> Subject: Re: I-D Action:draft-ietf-radext-design-13.txt
>=20
> Internet-Drafts@ietf.org wrote:
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the RADIUS EXTensions Working Group of the
> IETF.
> >=20
> >=20
> > 	Title           : RADIUS Design Guidelines
> > 	Author(s)       : G. Weber=2C A. DeKok
> > 	Filename        : draft-ietf-radext-design-13.txt
> > 	Pages           : 40
> > 	Date            : 2010-04-14
>=20
>   See also the 'diff' available at:
>=20
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-radext-design-13.txt
>=20
>   This revision incorporates suggestions from all open issues=2C includin=
g
> #327.
>=20
>   Please provide feedback.
>=20
>   Alan DeKok.
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
 		 	   		  =

--_1de28bcc-3e9d-4f65-87b0-855562c143b3_
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'>
Glancing at -13=2C there appear to be some inconsistencies within the text:=
<br><br>Section 1.3.1<br><br>As RADIUS has become more widely accepted as a=
 management protocol=2C<br>its usage has become more prevalent=2C both with=
in the IETF as well as<br>within other SDOs. Given the expanded utilization=
 of RADIUS=2C it has<br>become apparent that requiring SDOs to accomplish a=
ll their RADIUS<br>work within the IETF is inherently inefficient and unsca=
lable. By<br>articulating guidelines for RADIUS attribute design=2C this do=
cument<br>enables SDOs out of the IETF to design their own RADIUS attribute=
s<br>within the Vendor-Specific Attribute (VSA) space.<br><br>It is RECOMME=
NDED that SDOs follow the guidelines articulated in this<br>document. Howev=
er=2C we recognize that there are some situations where<br>SDOs or vendors =
require the creation of specifications not following<br>these guidelines. W=
e do not forbid these specifications=2C but it is<br>RECOMMENDED that they =
are created only if they have a limited scope<br>of applicability=2C and al=
l new attributes defined in those<br>specifications are VSAs. See Section 3=
=2C below=2C for additional<br>discussion of this topic.<br><br>It is RECOM=
MENDED that SDOs and vendors seek review of RADIUS<br>attribute specificati=
ons from the IETF. However=2C specifications do<br>not require IETF review =
when they satisfy all of the following<br>criteria:<br><br>* are SDO specif=
ic=3B<br><br>* reference attributes from pre-existing IETF or SDO<br>specif=
ications=3B<br><br>* define new attributes only in the VSA space=3B<br><br>=
* use only the "basic data types" (see below) for all VSAs=3B<br><br>* foll=
ow the guidelines given in this document.<br><br>[BA] This text is similar =
to text in Section 3.3.3=2C which leads me to<br>believe that there was an =
editing problem.<br>My suggestion is that the text in 3.3.3 be moved to Sec=
tion 1.3.1.<br><br>3.3.3. SDO Allocations<br><br>Given the expanded utiliza=
tion of RADIUS=2C it has become apparent that<br>requiring SDOs to accompli=
sh all their RADIUS work within the IETF is<br>inherently inefficient and u=
nscalable. Is is therefore RECOMMENDED<br>that SDO RADIUS Attribute specifi=
cations allocate attributes from the<br>vendor space=2C rather than request=
ing an allocation from the RADIUS<br>standard attribute space=2C for attrib=
utes matching any of the<br>following criteria:<br><br>* attributes relying=
 on data types not defined within RADIUS<br><br>* attributes intended prima=
rily for use within an SDO<br><br>* attributes intended primarily for use w=
ithin a group of SDOs.<br><br>Any new RADIUS attributes or values intended =
for interoperable use<br>across a broad spectrum of the Internet Community =
SHOULD follow the<br>allocation process defined in [RFC3575].<br><br>The re=
commendation for SDOs to allocate attributes from a vendor<br>space rather =
than via the IETF process is a recognition that SDOs<br>desire to assert ch=
ange control over their own RADIUS specifications.<br>This change control c=
an be obtained by requesting a PEC from the<br>Internet Assigned Number Aut=
hority (IANA)=2C for use as a Vendor-Id<br>within a Vendor-Specific attribu=
te. The SDO can then allocate<br>attributes within the VSA space defined by=
 that Vendor-Id=2C at their<br>sole discretion. Similarly=2C the use of dat=
a types (complex or<br>otherwise) within that VSA space is solely under the=
 discretion of<br>the SDO.<br><br>Nevertheless=2C following the guidelines =
outlined within this document<br>has many advantages. It is therefore RECOM=
MENDED that SDOs follow<br>the guidelines outlined here=2C which are intend=
ed to enable maximum<br>interoperability with minimal changes to existing s=
ystems.<br><br>[BA] The last paragraph does not appear to be consistent wit=
h Section 1.3=2C<br>so I'd<br>recommend that it be deleted.<br><br>3.3.2. V=
endor Allocations<br><br>Nevertheless=2C following the guidelines outlined =
within this document<br>has many advantages. It is therefore RECOMMENDED th=
at vendors follow<br>the guidelines outlined here=2C which are intended to =
enable maximum<br>interoperability with minimal changes to existing systems=
. If these<br>guidelines are not followed=2C the result will be increased c=
omplexity<br>with little or no benefit.<br><br>[BA] The resolution to Issue=
 327 recommended the following alternative text:<br><br>Nevertheless=2C fol=
lowing the guidelines outlined within this document<br>has several advantag=
es=2C including maximum interoperability with<br>minimal changes to existin=
g systems. Following these guidelines<br>means that RADIUS servers can be u=
pdated to support the vendor's<br>equipment by editing a RADIUS dictionary.=
 If these guidelines are<br>not followed=2C then the vendor's equipment can=
 only be supported<br>via code changes in RADIUS server implementations.<br=
>Such code changes add complexity and delay to implementations."<br><br>3.3=
.4. Publication of specifications<br><br>In order to enable IETF review of =
SDO specifications=2C it is<br>RECOMMENDED that:<br><br>* SDOs make their R=
ADIUS attribute specifications publicly<br>available=3B<br><br>* SDOs reque=
st review of RADIUS attribute specifications by<br>sending email to the AAA=
 Doctors [DOCTORS] or equivalent mailing<br>list=3B<br><br>* IETF and SDO R=
ADIUS attribute specifications are reviewed<br>according to the guidelines =
proposed in this document=3B<br><br>* Reviews of specifications are posted =
to the RADEXT WG mailing<br>list=2C<br>the AAA Doctors mailing list [DOCTOR=
S] or another IETF mailing<br>list<br>suggested by the Operations &amp=3B M=
anagement Area Directors of the<br>IETF.<br><br>It should be understood tha=
t SDOs do not have to rehost VSAs into the<br>standards space solely for th=
e purpose of obtaining IETF review.<br>Rehosting puts pressure on the stand=
ards space=2C and may be harmful to<br>interoperability=2C since it can cre=
ate two ways to provision the same<br>service. Rehosting may also require c=
hanges to the RADIUS data model<br>which will affect implementations that d=
o not intend to support the<br>SDO specifications.<br><br>These reviews can=
 assist with creation of specifications that meet<br>the SDO requirements=
=2C and which are also compatible with the<br>traditional data model and us=
es of RADIUS. While these reviews<br>require access to public specification=
s=2C the review process does not<br>require publication of an IETF RFC.<br>=
<br>SDOs are encouraged to seek early review of their specifications by<br>=
the IETF. It should be understood that reviews are a voluntary-based<br>ser=
vice offered on best-effort basis.<br><br>Where the RADIUS specification is=
 embedded within a larger document<br>which cannot be made public=2C the RA=
DIUS attribute and value<br>definitions SHOULD be published instead as an I=
nformational RFC=2C as<br>with [RFC4679]. This process SHOULD be followed i=
nstead of<br>requesting IANA allocations from within the standard RADIUS at=
tribute<br>space.<br><br>Similarly=2C vendors are encouraged to make their =
specifications<br>publicly available=2C for maximum interoperability. Howev=
er=2C it is not<br>necessary for them to request publication of their VSA s=
pecifications<br>as Informational RFCs by the IETF.<br><br>All other specif=
ications=2C including new authentication=2C<br>authorization=2C and/or secu=
rity mechanisms SHOULD follow the<br>allocation process defined in [RFC3575=
].<br><br>[BA] The resolution to Issue 327 recommended the following altern=
ative text:<br><br>SDOs or vendors desiring review of their RADIUS specific=
ations<br>by the IETF are encouraged to seek review as early as possible=2C=
<br>so as to avoid potential delays. Since reviews are handled by volunteer=
s=2C<br>responses are provided on a best-effort basis=2C with no service<br=
>level guarantees. In order to provide reviewers with access to the<br>spec=
ification=2C SDOs and vendors are encouraged to make them publicly<br>avail=
able.<br>Where the RADIUS specification is embedded within a larger documen=
t which<br>cannot be made public=2C the RADIUS attribute and value definiti=
ons<br>can be made available on a public web site or can be published as<br=
>an Informational RFC=2C as with [RFC4679].<br><br>Review can be requested =
by sending email to the AAA Doctors [DOCTORS]<br>or equivalent mailing list=
. The IETF Operations &amp=3B Management<br>Area Directors will then arrang=
e for the review to be<br>completed and posted to the AAA Doctors mailing l=
ist<br>[DOCTORS]=2C RADEXT WG mailing list=2C or other IETF mailing<br>list=
.<br><br>The review process requires neither allocation of attributes<br>wi=
thin the IETF standard attribute space nor publication of an<br>IETF RFC. R=
equiring SDOs or vendors to rehost VSAs into the IETF standards<br>attribut=
e space solely for the purpose of obtaining review<br>would put pressure on=
 the standards space=2C and may be harmful to<br>interoperability=2C since =
it can create two ways to provision the same<br>service. Rehosting may also=
 require changes to the RADIUS data model<br>which will affect implementati=
ons that do not intend to support the<br>SDO or vendor specifications."<br>=
<br>&gt=3B -----Original Message-----<br>&gt=3B From: owner-radiusext@ops.i=
etf.org [mailto:owner-radiusext@ops.ietf.org] On<br>&gt=3B Behalf Of Alan D=
eKok<br>&gt=3B Sent: Wednesday=2C April 14=2C 2010 5:55 AM<br>&gt=3B To: ra=
diusext@ops.ietf.org<br>&gt=3B Subject: Re: I-D Action:draft-ietf-radext-de=
sign-13.txt<br>&gt=3B <br>&gt=3B Internet-Drafts@ietf.org wrote:<br>&gt=3B =
&gt=3B A New Internet-Draft is available from the on-line Internet-Drafts<b=
r>&gt=3B directories.<br>&gt=3B &gt=3B This draft is a work item of the RAD=
IUS EXTensions Working Group of the<br>&gt=3B IETF.<br>&gt=3B &gt=3B <br>&g=
t=3B &gt=3B <br>&gt=3B &gt=3B 	Title           : RADIUS Design Guidelines<b=
r>&gt=3B &gt=3B 	Author(s)       : G. Weber=2C A. DeKok<br>&gt=3B &gt=3B 	F=
ilename        : draft-ietf-radext-design-13.txt<br>&gt=3B &gt=3B 	Pages   =
        : 40<br>&gt=3B &gt=3B 	Date            : 2010-04-14<br>&gt=3B <br>&=
gt=3B   See also the 'diff' available at:<br>&gt=3B <br>&gt=3B http://tools=
.ietf.org/rfcdiff?url2=3Ddraft-ietf-radext-design-13.txt<br>&gt=3B <br>&gt=
=3B   This revision incorporates suggestions from all open issues=2C includ=
ing<br>&gt=3B #327.<br>&gt=3B <br>&gt=3B   Please provide feedback.<br>&gt=
=3B <br>&gt=3B   Alan DeKok.<br>&gt=3B <br>&gt=3B --<br>&gt=3B to unsubscri=
be send a message to radiusext-request@ops.ietf.org with<br>&gt=3B the word=
 'unsubscribe' in a single line as the message text body.<br>&gt=3B archive=
: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br> 		 	   		  </body>
</html>=

--_1de28bcc-3e9d-4f65-87b0-855562c143b3_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 16 07:45: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 3987C3A68EA for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 16 Apr 2010 07:45:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.13
X-Spam-Level: *
X-Spam-Status: No, score=1.13 tagged_above=-999 required=5 tests=[AWL=-0.975, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UmqbcNzljVCN for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 16 Apr 2010 07:45:03 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6389F28C0CF for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 16 Apr 2010 07:45:01 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O2meT-000051-M3 for radiusext-data0@psg.com; Fri, 16 Apr 2010 14:36:13 +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 1O2meO-000047-5A for radiusext@ops.ietf.org; Fri, 16 Apr 2010 14:36:08 +0000
Message-ID: <4BC875D5.1060802@deployingradius.com>
Date: Fri, 16 Apr 2010 16:36:05 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: I-D Action:draft-ietf-radext-design-13.txt
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl>
In-Reply-To: <BLU137-W3272B8995285C2B99C9DF0930F0@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:
> Glancing at -13, there appear to be some inconsistencies within the text:
> 
> Section 1.3.1
...
> [BA] This text is similar to text in Section 3.3.3, which leads me to
> believe that there was an editing problem.

  The intent was to start off defining situations where SDOs did *not*
require review, and to later discuss situations where they did need review.

> My suggestion is that the text in 3.3.3 be moved to Section 1.3.1.

  Hmm... it's substantially similar to 3.3.2, but directed towards SDOs
rather than vendors.  I'd prefer to leave it where it is, but there are
arguments to be made both ways.

> Nevertheless, following the guidelines outlined within this document
> has many advantages. It is therefore RECOMMENDED that SDOs follow
> the guidelines outlined here, which are intended to enable maximum
> interoperability with minimal changes to existing systems.
> 
> [BA] The last paragraph does not appear to be consistent with Section 1.3,
> so I'd
> recommend that it be deleted.

  I'm not sure what isn't consistent, but OK.

> 3.3.2. Vendor Allocations
> 
> Nevertheless, following the guidelines outlined within this document
> has many advantages. It is therefore RECOMMENDED that vendors follow
> the guidelines outlined here, which are intended to enable maximum
> interoperability with minimal changes to existing systems. If these
> guidelines are not followed, the result will be increased complexity
> with little or no benefit.
> 
> [BA] The resolution to Issue 327 recommended the following alternative text:

  OK.  I was trying to avoid repeating the discussion on dictionaries
and code changes...

> 3.3.4. Publication of specifications
...
> [BA] The resolution to Issue 327 recommended the following alternative text:

  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  Mon Apr 19 09:25: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 B119328C1BB for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 19 Apr 2010 09:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.265
X-Spam-Level: *
X-Spam-Status: No, score=1.265 tagged_above=-999 required=5 tests=[AWL=-0.841, 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 q6mfhwjxEjxf for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 19 Apr 2010 09:25:05 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id C9DC63A6B96 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 19 Apr 2010 09:01:54 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O3tLm-000KZg-PH for radiusext-data0@psg.com; Mon, 19 Apr 2010 15:57:30 +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 1O3tLk-000KZI-Gt for radiusext@ops.ietf.org; Mon, 19 Apr 2010 15:57:28 +0000
Received: from BLU137-W6 ([65.55.116.8]) by blu0-omc1-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 19 Apr 2010 08:57:27 -0700
Message-ID: <BLU137-W64CCF24BD8E6473D2F0AE930B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_96f5e7e6-23ed-451e-9199-83ca09bd3329_"
X-Originating-IP: [24.19.160.219]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: nits: draft-ietf-radext-status-server
Date: Mon, 19 Apr 2010 08:57:27 -0700
Importance: Normal
In-Reply-To: <32992EDA-77AA-4EEF-8BD6-6CE9DBFB5B5F@nokia.com>
References: <32992EDA-77AA-4EEF-8BD6-6CE9DBFB5B5F@nokia.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 19 Apr 2010 15:57:27.0827 (UTC) FILETIME=[029DBE30:01CADFD9]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_96f5e7e6-23ed-451e-9199-83ca09bd3329_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



> From: lars.eggert@nokia.com
> Date: Mon=2C 19 Apr 2010 17:07:54 +0300
> To: draft-ietf-radext-status-server@tools.ietf.org=3B radext-chairs@tools=
.ietf.org=3B radext-ads@tools.ietf.org
> Subject: nits: draft-ietf-radext-status-server=20
>=20
>   Note: Most comments marked as "nits" below have been automatically
>  flagged by review scripts - there may be some false positives in there.
>=20
>=20
>=20
> Section 4.1.=2C paragraph 9:
> >    to send Request packets.  In that case=2C the Identifer field MUST b=
e
>=20
>   Nit: s/Identifer/Identifier/
>=20
>=20
> Section 4.2.=2C paragraph 1:
> >    it is enabled.  Servers SHOULD also permit adminstrators to enable o=
r
>=20
>   Nit: s/adminstrators/administrators/
>=20
>=20
>=20
> Section 4.3.=2C paragraph 4:
> >    accounting ports.  The client MUST treat each destination (ip=2C por=
t)
>=20
>   Nit: s/(ip=2C/(IP=2C/
>=20
>=20
> Section 4.5.=2C paragraph 4:
> >    Each RADIUS Proxyhas relationships with RADIUS Servers for both Real=
m
>=20
>   Nit: s/Proxyhas/Proxy has/
>=20
>=20
> Section 0=2C paragraph 0:
> >    0        0        0            70   EAP-MEssage
>=20
>   Nit: s/EAP-MEssage/EAP-Message/
>=20
>=20
 		 	   		  =

--_96f5e7e6-23ed-451e-9199-83ca09bd3329_
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'>
<br>&gt=3B From: lars.eggert@nokia.com<br>&gt=3B Date: Mon=2C 19 Apr 2010 1=
7:07:54 +0300<br>&gt=3B To: draft-ietf-radext-status-server@tools.ietf.org=
=3B radext-chairs@tools.ietf.org=3B radext-ads@tools.ietf.org<br>&gt=3B Sub=
ject: nits: draft-ietf-radext-status-server <br>&gt=3B <br>&gt=3B   Note: M=
ost comments marked as "nits" below have been automatically<br>&gt=3B  flag=
ged by review scripts - there may be some false positives in there.<br>&gt=
=3B <br>&gt=3B <br>&gt=3B <br>&gt=3B Section 4.1.=2C paragraph 9:<br>&gt=3B=
 &gt=3B    to send Request packets.  In that case=2C the Identifer field MU=
ST be<br>&gt=3B <br>&gt=3B   Nit: s/Identifer/Identifier/<br>&gt=3B <br>&gt=
=3B <br>&gt=3B Section 4.2.=2C paragraph 1:<br>&gt=3B &gt=3B    it is enabl=
ed.  Servers SHOULD also permit adminstrators to enable or<br>&gt=3B <br>&g=
t=3B   Nit: s/adminstrators/administrators/<br>&gt=3B <br>&gt=3B <br>&gt=3B=
 <br>&gt=3B Section 4.3.=2C paragraph 4:<br>&gt=3B &gt=3B    accounting por=
ts.  The client MUST treat each destination (ip=2C port)<br>&gt=3B <br>&gt=
=3B   Nit: s/(ip=2C/(IP=2C/<br>&gt=3B <br>&gt=3B <br>&gt=3B Section 4.5.=2C=
 paragraph 4:<br>&gt=3B &gt=3B    Each RADIUS Proxyhas relationships with R=
ADIUS Servers for both Realm<br>&gt=3B <br>&gt=3B   Nit: s/Proxyhas/Proxy h=
as/<br>&gt=3B <br>&gt=3B <br>&gt=3B Section 0=2C paragraph 0:<br>&gt=3B &gt=
=3B    0        0        0            70   EAP-MEssage<br>&gt=3B <br>&gt=3B=
   Nit: s/EAP-MEssage/EAP-Message/<br>&gt=3B <br>&gt=3B <br> 		 	   		  </b=
ody>
</html>=

--_96f5e7e6-23ed-451e-9199-83ca09bd3329_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 19 09:25:08 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6303B28C3C6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 19 Apr 2010 09:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.287
X-Spam-Level: *
X-Spam-Status: No, score=1.287 tagged_above=-999 required=5 tests=[AWL=-0.819, 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 GERZLTwMO1WC for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 19 Apr 2010 09:25:07 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id C9DA13A6B7A for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 19 Apr 2010 09:01:54 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O3tMI-000Ke0-9B for radiusext-data0@psg.com; Mon, 19 Apr 2010 15:58:02 +0000
Received: from [65.55.116.37] (helo=blu0-omc1-s26.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1O3tMF-000Kdj-Np for radiusext@ops.ietf.org; Mon, 19 Apr 2010 15:57:59 +0000
Received: from BLU137-W30 ([65.55.116.7]) by blu0-omc1-s26.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 19 Apr 2010 08:57:59 -0700
Message-ID: <BLU137-W30DADD024EF4A551174538930B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_39957140-d247-490a-96de-5f1c03b449f8_"
X-Originating-IP: [24.19.160.219]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: DISCUSS and COMMENT: draft-ietf-radext-status-server
Date: Mon, 19 Apr 2010 08:57:58 -0700
Importance: Normal
In-Reply-To: <20100419135854.3D26428C112@core3.amsl.com>
References: <20100419135854.3D26428C112@core3.amsl.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 19 Apr 2010 15:57:59.0115 (UTC) FILETIME=[1543E9B0:01CADFD9]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_39957140-d247-490a-96de-5f1c03b449f8_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



> From: lars.eggert@nokia.com
> To: iesg@ietf.org
> CC: radext-chairs@tools.ietf.org=3B draft-ietf-radext-status-server@tools=
.ietf.org
> Date: Mon=2C 19 Apr 2010 06:58:54 -0700
> Subject: DISCUSS and COMMENT: draft-ietf-radext-status-server=20
>=20
> Discuss:
>=20
> Section 4.1.=2C paragraph 2:
> >    The client SHOULD also have a configurable global timer (Tw) that is
> >    used when sending periodic Status-Server queries during server fail-
> >    over.  The default value SHOULD be 30 seconds=2C and the value MUST =
NOT
> >    be permitted to be set below 6 seconds.  If a response has not been
> >    received within the timeout period=2C the Status-Server packet is
> >    deemed to have received no corresponding Response packet=2C and MUST=
 be
> >    discarded.
>=20
>   DISCUSS: I would like to discuss two issues with this design. First=2C
>   since it is only RECOMMENDED to implement Tw and not REQUIRED=2C client=
s
>   need not do so. How do clients without Tw decide that a server has not
>   responded?
>=20
>   Second=2C there is no discussion on what rate clients should
>   be using when *issuing* Status-Server queries. The current text allows
>   a client to send Status-Server queries to the server at high rates=2C
>   and does not require the client to reduce its sending rate when it
>   receives no responses. In other words=2C there currently isn't any sort
>   of congestion control. Has this been discussed by the working group?
>   It seems like all the pieces are already there to implement a simple
>   congestion control scheme: have clients issue at most one request per
>   Tw (already implied by Section 4.3 text but not clearly stated
>   anywhere)=2C double Tw up to some conservative maximum when the server
>   does not respond=2C restore the initial Tw when it does (Section 4.3
>   again has some text that goes into that direction).
>=20
> Comment:
>=20
> Section 1812.=2C paragraph 4:
>=20
> >    The server MAY prioritize the handling of Status-Server packets over
> >    the handling of other requests=2C subject to the rate limiting
> >    described above.
>=20
>   Without congestion control=2C implementing this MAY guarantees that the
>   minimum amount of useful (=3D non-Status-Server) work will be done.
>=20
>=20
> Section 4.3.=2C paragraph 3:
> >    If no response is received to Status-Server packets=2C the RADIUS
> >    client can initiate failover to another proxy.  By continuing to sen=
d
> >    Status-Server packets to the original proxy at an interval of Tw=2C =
the
> >    RADIUS client can determine when the original proxy becomes
> >    responsive again.
>=20
>   This uses Status-Server messages as an overload detection mechanism.
>   They need to be sent in a way that will back off the rate
>   under overload=2C because otherwise the scheme can turn into an
>   overload *generation* mechanism.
>=20
>=20
> Section 4.5.=2C paragraph 17:
> >    It is RECOMMENDED=2C therefore=2C that implementations desiring the =
most
> >    benefit from Status-Server also implement server failover.  The
> >    combination of these two practices will maximize network reliability
> >    and stability.
>=20
>   If Status-Server messages are being sent in a way that is congestion
>   controlled (i.e.=2C the rate is reduced under overload).
>=20
 		 	   		  =

--_39957140-d247-490a-96de-5f1c03b449f8_
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'>
<br>&gt=3B From: lars.eggert@nokia.com<br>&gt=3B To: iesg@ietf.org<br>&gt=
=3B CC: radext-chairs@tools.ietf.org=3B draft-ietf-radext-status-server@too=
ls.ietf.org<br>&gt=3B Date: Mon=2C 19 Apr 2010 06:58:54 -0700<br>&gt=3B Sub=
ject: DISCUSS and COMMENT: draft-ietf-radext-status-server <br>&gt=3B <br>&=
gt=3B Discuss:<br>&gt=3B <br>&gt=3B Section 4.1.=2C paragraph 2:<br>&gt=3B =
&gt=3B    The client SHOULD also have a configurable global timer (Tw) that=
 is<br>&gt=3B &gt=3B    used when sending periodic Status-Server queries du=
ring server fail-<br>&gt=3B &gt=3B    over.  The default value SHOULD be 30=
 seconds=2C and the value MUST NOT<br>&gt=3B &gt=3B    be permitted to be s=
et below 6 seconds.  If a response has not been<br>&gt=3B &gt=3B    receive=
d within the timeout period=2C the Status-Server packet is<br>&gt=3B &gt=3B=
    deemed to have received no corresponding Response packet=2C and MUST be=
<br>&gt=3B &gt=3B    discarded.<br>&gt=3B <br>&gt=3B   DISCUSS: I would lik=
e to discuss two issues with this design. First=2C<br>&gt=3B   since it is =
only RECOMMENDED to implement Tw and not REQUIRED=2C clients<br>&gt=3B   ne=
ed not do so. How do clients without Tw decide that a server has not<br>&gt=
=3B   responded?<br>&gt=3B <br>&gt=3B   Second=2C there is no discussion on=
 what rate clients should<br>&gt=3B   be using when *issuing* Status-Server=
 queries. The current text allows<br>&gt=3B   a client to send Status-Serve=
r queries to the server at high rates=2C<br>&gt=3B   and does not require t=
he client to reduce its sending rate when it<br>&gt=3B   receives no respon=
ses. In other words=2C there currently isn't any sort<br>&gt=3B   of conges=
tion control. Has this been discussed by the working group?<br>&gt=3B   It =
seems like all the pieces are already there to implement a simple<br>&gt=3B=
   congestion control scheme: have clients issue at most one request per<br=
>&gt=3B   Tw (already implied by Section 4.3 text but not clearly stated<br=
>&gt=3B   anywhere)=2C double Tw up to some conservative maximum when the s=
erver<br>&gt=3B   does not respond=2C restore the initial Tw when it does (=
Section 4.3<br>&gt=3B   again has some text that goes into that direction).=
<br>&gt=3B <br>&gt=3B Comment:<br>&gt=3B <br>&gt=3B Section 1812.=2C paragr=
aph 4:<br>&gt=3B <br>&gt=3B &gt=3B    The server MAY prioritize the handlin=
g of Status-Server packets over<br>&gt=3B &gt=3B    the handling of other r=
equests=2C subject to the rate limiting<br>&gt=3B &gt=3B    described above=
.<br>&gt=3B <br>&gt=3B   Without congestion control=2C implementing this MA=
Y guarantees that the<br>&gt=3B   minimum amount of useful (=3D non-Status-=
Server) work will be done.<br>&gt=3B <br>&gt=3B <br>&gt=3B Section 4.3.=2C =
paragraph 3:<br>&gt=3B &gt=3B    If no response is received to Status-Serve=
r packets=2C the RADIUS<br>&gt=3B &gt=3B    client can initiate failover to=
 another proxy.  By continuing to send<br>&gt=3B &gt=3B    Status-Server pa=
ckets to the original proxy at an interval of Tw=2C the<br>&gt=3B &gt=3B   =
 RADIUS client can determine when the original proxy becomes<br>&gt=3B &gt=
=3B    responsive again.<br>&gt=3B <br>&gt=3B   This uses Status-Server mes=
sages as an overload detection mechanism.<br>&gt=3B   They need to be sent =
in a way that will back off the rate<br>&gt=3B   under overload=2C because =
otherwise the scheme can turn into an<br>&gt=3B   overload *generation* mec=
hanism.<br>&gt=3B <br>&gt=3B <br>&gt=3B Section 4.5.=2C paragraph 17:<br>&g=
t=3B &gt=3B    It is RECOMMENDED=2C therefore=2C that implementations desir=
ing the most<br>&gt=3B &gt=3B    benefit from Status-Server also implement =
server failover.  The<br>&gt=3B &gt=3B    combination of these two practice=
s will maximize network reliability<br>&gt=3B &gt=3B    and stability.<br>&=
gt=3B <br>&gt=3B   If Status-Server messages are being sent in a way that i=
s congestion<br>&gt=3B   controlled (i.e.=2C the rate is reduced under over=
load).<br>&gt=3B <br> 		 	   		  </body>
</html>=

--_39957140-d247-490a-96de-5f1c03b449f8_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 20 14:06:32 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9216A28C107 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 20 Apr 2010 14:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.301
X-Spam-Level: *
X-Spam-Status: No, score=1.301 tagged_above=-999 required=5 tests=[AWL=-0.804, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwwEPQGjMA89 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 20 Apr 2010 14:06:31 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 71F2D3A6959 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 20 Apr 2010 14:06:28 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O4KZ3-000Du7-GG for radiusext-data0@psg.com; Tue, 20 Apr 2010 21:01:01 +0000
Received: from [65.55.116.13] (helo=blu0-omc1-s2.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1O4KYy-000Dta-EO for radiusext@ops.ietf.org; Tue, 20 Apr 2010 21:00:56 +0000
Received: from BLU137-DS10 ([65.55.116.7]) by blu0-omc1-s2.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 20 Apr 2010 14:00:56 -0700
X-Originating-IP: [131.107.0.74]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS1074803E73A527CFB4BF31930A0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
References: <20100420183124.E173B3A683F@core3.amsl.com>
In-Reply-To: <20100420183124.E173B3A683F@core3.amsl.com>
Subject: DISCUSS and COMMENT: draft-ietf-radext-status-server 
Date: Tue, 20 Apr 2010 14:00:54 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH+QAViIud9GCSFTz6M9KPhOW92qpHFGQqQ
Content-Language: en-us
X-OriginalArrivalTime: 20 Apr 2010 21:00:56.0095 (UTC) FILETIME=[9200B2F0:01CAE0CC]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

-----Original Message-----
From: Peter Saint-Andre [mailto:stpeter@stpeter.im]=20
Sent: Tuesday, April 20, 2010 11:31 AM
To: iesg@ietf.org
Cc: aland@freeradius.org; radext-chairs@tools.ietf.org; =
draft-ietf-radext-status-server@tools.ietf.org
Subject: DISCUSS and COMMENT: draft-ietf-radext-status-server=20

Discuss:
Is the use of MD5 in generating the Response Authenticator subject to =
collision attacks? If not, it would be helpful to describe why not, and =
provide a reference to RFC 4270. If so, then the security considerations =
need to be updated.

Comment:
Given that the Request Authenticator should be unpredictable and unique, =
a reference to RFC 4086 would be appropriate.

Please add a reference to RFC 1321 for the definition of MD5.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 21 15:24: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 A9C693A6A3A for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 21 Apr 2010 15:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.32
X-Spam-Level: *
X-Spam-Status: No, score=1.32 tagged_above=-999 required=5 tests=[AWL=-0.786, 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 71B8JrkjN9Vb for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 21 Apr 2010 15:24:58 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id CC7BD3A6B2F for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 21 Apr 2010 15:24:09 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O4iH1-0001um-2y for radiusext-data0@psg.com; Wed, 21 Apr 2010 22:19:59 +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 1O4iGx-0001uS-Me for radiusext@ops.ietf.org; Wed, 21 Apr 2010 22:19:55 +0000
Received: from BLU137-W7 ([65.55.116.9]) by blu0-omc1-s22.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Apr 2010 15:19:55 -0700
Message-ID: <BLU137-W7892528D73B56E7638DD493090@phx.gbl>
Content-Type: multipart/alternative; boundary="_b8c58574-3e51-4c71-a9fe-026822cca349_"
X-Originating-IP: [131.107.0.69]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: COMMENT: draft-ietf-radext-status-server
Date: Wed, 21 Apr 2010 15:19:54 -0700
Importance: Normal
In-Reply-To: <20100421214340.DD29728C0E0@core3.amsl.com>
References: <20100421214340.DD29728C0E0@core3.amsl.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 21 Apr 2010 22:19:55.0099 (UTC) FILETIME=[C51512B0:01CAE1A0]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_b8c58574-3e51-4c71-a9fe-026822cca349_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



> From: turners@ieca.com
> To: iesg@ietf.org
> CC: radext-chairs@tools.ietf.org=3B draft-ietf-radext-status-server@tools=
.ietf.org
> Date: Wed=2C 21 Apr 2010 14:43:40 -0700
> Subject: COMMENT: draft-ietf-radext-status-server=20
>=20
> Comment:
> I support Peter's discuss. =20
>=20
> Additionally=2C I noted the same thing Peter did wrt to random numbers.
>=20
> Section 3: In the Request Authenticator description the two paragraphs re=
peat that Request Authentication SHOULD be unpredictable and then says why.=
 Maybe the second paragraph should be tweaked:
>=20
>  The Request Authenticator value in a Status-Server packet
>  SHOULD also be unpredictable **because** an attacker **could**
>  trick a server
>  into responding to a predicted future request=2C and then use the
>  response to masquerade as that server to a future Status-Server
>  request from a client.
>=20
 		 	   		  =

--_b8c58574-3e51-4c71-a9fe-026822cca349_
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'>
<br>&gt=3B From: turners@ieca.com<br>&gt=3B To: iesg@ietf.org<br>&gt=3B CC:=
 radext-chairs@tools.ietf.org=3B draft-ietf-radext-status-server@tools.ietf=
.org<br>&gt=3B Date: Wed=2C 21 Apr 2010 14:43:40 -0700<br>&gt=3B Subject: C=
OMMENT: draft-ietf-radext-status-server <br>&gt=3B <br>&gt=3B Comment:<br>&=
gt=3B I support Peter's discuss.  <br>&gt=3B <br>&gt=3B Additionally=2C I n=
oted the same thing Peter did wrt to random numbers.<br>&gt=3B <br>&gt=3B S=
ection 3: In the Request Authenticator description the two paragraphs repea=
t that Request Authentication SHOULD be unpredictable and then says why. Ma=
ybe the second paragraph should be tweaked:<br>&gt=3B <br>&gt=3B  The Reque=
st Authenticator value in a Status-Server packet<br>&gt=3B  SHOULD also be =
unpredictable **because** an attacker **could**<br>&gt=3B  trick a server<b=
r>&gt=3B  into responding to a predicted future request=2C and then use the=
<br>&gt=3B  response to masquerade as that server to a future Status-Server=
<br>&gt=3B  request from a client.<br>&gt=3B <br> 		 	   		  </body>
</html>=

--_b8c58574-3e51-4c71-a9fe-026822cca349_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 21 18:28: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 649363A690F for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 21 Apr 2010 18:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.339
X-Spam-Level: *
X-Spam-Status: No, score=1.339 tagged_above=-999 required=5 tests=[AWL=-0.767, 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 6HubAQHSLYDH for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 21 Apr 2010 18:28:51 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 3AFA53A67F0 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 21 Apr 2010 18:28:51 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O4lAW-000Aj0-31 for radiusext-data0@psg.com; Thu, 22 Apr 2010 01:25:28 +0000
Received: from [65.55.116.34] (helo=blu0-omc1-s23.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1O4lAT-000AiW-39 for radiusext@ops.ietf.org; Thu, 22 Apr 2010 01:25:25 +0000
Received: from BLU137-W6 ([65.55.116.9]) by blu0-omc1-s23.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Apr 2010 18:25:24 -0700
Message-ID: <BLU137-W66E08672FD489DD69AF5A93080@phx.gbl>
Content-Type: multipart/alternative; boundary="_23987067-6fc3-48d5-8453-1148c1a5d6cc_"
X-Originating-IP: [131.107.0.71]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: COMMENT: draft-ietf-radext-status-server
Date: Wed, 21 Apr 2010 18:25:24 -0700
Importance: Normal
In-Reply-To: <20100422012225.139A33A696D@core3.amsl.com>
References: <20100422012225.139A33A696D@core3.amsl.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 22 Apr 2010 01:25:24.0400 (UTC) FILETIME=[AEA9A300:01CAE1BA]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_23987067-6fc3-48d5-8453-1148c1a5d6cc_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



> From: housley@vigilsec.com
> To: iesg@ietf.org
> CC: Francis.Dupont@fdupont.fr=3B radext-chairs@tools.ietf.org=3B draft-ie=
tf-radext-status-server@tools.ietf.org
> Date: Wed=2C 21 Apr 2010 18:22:24 -0700
> Subject: COMMENT: draft-ietf-radext-status-server=20
>=20
> Comment:
>=20
> Please consider the comments from the Gen-ART Review by Francis Dupont:
>=20
> - Abstract page 2: there is an explicit reference to a RFC=2C this is in
> general forbidden but IMHO we are here in the allowed exception case.
>=20
> - 2.1.1 page 8: a servers policy -> a server policy
>=20
> - 3 page 10 (twice): etc. -> etc.=2C ???
>=20
> - 4.2 page 13: adminstrators -> administrators
>=20
> - 4.2 page 15 (twice): e.g. -> e.g.=2C
>=20
> - 4.3 page 16: modelled -> modeled
>=20
> - 4.3 page 16: usually the hysteresis against flapping tries to keep
> the connection (i.e.=2C failover after 3 missed responses)=2C here it is
> the opposite. IMHO it is very aggressive but it is how RFC 3539 works
> so I have no concern about it.
>=20
> - 4.5 page 16: Proxyhas -> Proxy has
>=20
> - 4.5 page 17: cannot=2C -> cannot
>=20
> - 4.5 page 18: i.e. -> i.e.=2C
>=20
> - 5 page 19: EAP-MEssage -> EAP-Message
>=20
> - 8 page 23: synthesise -> synthesize
>=20
> - 8 page 23: in "the suggestion of [RFC5080] Section 2.2.2=2C which sugge=
sts"
> suggests -> proposes
>=20
> - 8 page 23: configurably is not in my dict?
>=20
> - 9.2 page 23: IMHO the RFC2119 reference should be moved to normative
> references section (perhaps others too?)
>=20
> - Authors' Addresses -> Author's Address
>=20

 		 	   		  =

--_23987067-6fc3-48d5-8453-1148c1a5d6cc_
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'>
<BR>&gt=3B From: housley@vigilsec.com<BR>&gt=3B To: iesg@ietf.org<BR>&gt=3B=
 CC: Francis.Dupont@fdupont.fr=3B radext-chairs@tools.ietf.org=3B draft-iet=
f-radext-status-server@tools.ietf.org<BR>&gt=3B Date: Wed=2C 21 Apr 2010 18=
:22:24 -0700<BR>&gt=3B Subject: COMMENT: draft-ietf-radext-status-server <B=
R>&gt=3B <BR>&gt=3B Comment:<BR>&gt=3B <BR>&gt=3B Please consider the comme=
nts from the Gen-ART Review by Francis Dupont:<BR>&gt=3B <BR>&gt=3B - Abstr=
act page 2: there is an explicit reference to a RFC=2C this is in<BR>&gt=3B=
 general forbidden but IMHO we are here in the allowed exception case.<BR>&=
gt=3B <BR>&gt=3B - 2.1.1 page 8: a servers policy -&gt=3B a server policy<B=
R>&gt=3B <BR>&gt=3B - 3 page 10 (twice): etc. -&gt=3B etc.=2C ???<BR>&gt=3B=
 <BR>&gt=3B - 4.2 page 13: adminstrators -&gt=3B administrators<BR>&gt=3B <=
BR>&gt=3B - 4.2 page 15 (twice): e.g. -&gt=3B e.g.=2C<BR>&gt=3B <BR>&gt=3B =
- 4.3 page 16: modelled -&gt=3B modeled<BR>&gt=3B <BR>&gt=3B - 4.3 page 16:=
 usually the hysteresis against flapping tries to keep<BR>&gt=3B the connec=
tion (i.e.=2C failover after 3 missed responses)=2C here it is<BR>&gt=3B th=
e opposite. IMHO it is very aggressive but it is how RFC 3539 works<BR>&gt=
=3B so I have no concern about it.<BR>&gt=3B <BR>&gt=3B - 4.5 page 16: Prox=
yhas -&gt=3B Proxy has<BR>&gt=3B <BR>&gt=3B - 4.5 page 17: cannot=2C -&gt=
=3B cannot<BR>&gt=3B <BR>&gt=3B - 4.5 page 18: i.e. -&gt=3B i.e.=2C<BR>&gt=
=3B <BR>&gt=3B - 5 page 19: EAP-MEssage -&gt=3B EAP-Message<BR>&gt=3B <BR>&=
gt=3B - 8 page 23: synthesise -&gt=3B synthesize<BR>&gt=3B <BR>&gt=3B - 8 p=
age 23: in "the suggestion of [RFC5080] Section 2.2.2=2C which suggests"<BR=
>&gt=3B suggests -&gt=3B proposes<BR>&gt=3B <BR>&gt=3B - 8 page 23: configu=
rably is not in my dict?<BR>&gt=3B <BR>&gt=3B - 9.2 page 23: IMHO the RFC21=
19 reference should be moved to normative<BR>&gt=3B references section (per=
haps others too?)<BR>&gt=3B <BR>&gt=3B - Authors' Addresses -&gt=3B Author'=
s Address<BR>&gt=3B <BR><BR> 		 	   		  </body>
</html>=

--_23987067-6fc3-48d5-8453-1148c1a5d6cc_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 22 01:08:38 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A324B3A68D5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 22 Apr 2010 01:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.331
X-Spam-Level: 
X-Spam-Status: No, score=-0.331 tagged_above=-999 required=5 tests=[AWL=-1.696, BAYES_20=-0.74, 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 k8y3bKprb65a for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 22 Apr 2010 01:08:37 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 752493A6852 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 22 Apr 2010 01:08:35 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O4rOJ-0006uf-OJ for radiusext-data0@psg.com; Thu, 22 Apr 2010 08:04:07 +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 1O4rOG-0006qL-9l for radiusext@ops.ietf.org; Thu, 22 Apr 2010 08:04:04 +0000
X-IronPort-AV: E=Sophos;i="4.52,255,1270440000";  d="scan'208,217";a="185425915"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 22 Apr 2010 04:04:00 -0400
X-IronPort-AV: E=Sophos;i="4.52,255,1270440000";  d="scan'208,217";a="466803705"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by co300216-co-erhwest-out.avaya.com with ESMTP; 22 Apr 2010 04:03:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAE1F2.5316F534"
Subject: RE: COMMENT: draft-ietf-radext-status-server
Date: Thu, 22 Apr 2010 10:03:41 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402103ED0@307622ANEX5.global.avaya.com>
In-Reply-To: <BLU137-W66E08672FD489DD69AF5A93080@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: COMMENT: draft-ietf-radext-status-server
Thread-Index: AcrhutvV56TC0t3wRcCDnGH97WYhGAAN0MAA
References: <20100422012225.139A33A696D@core3.amsl.com> <BLU137-W66E08672FD489DD69AF5A93080@phx.gbl>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Alan DeKok" <aland@deployingradius.com>
Cc: "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_01CAE1F2.5316F534
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Alan,
=20
I have not seen any response from you to the issues raised in the
DISCUSS and COMMENT made by the different AD's. The IESG telechat is
scheduled for today at 11:30AM ET. Are you on line and preparing answers
to the issues raised?=20
=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: Thursday, April 22, 2010 4:25 AM
	To: radiusext@ops.ietf.org
	Subject: COMMENT: draft-ietf-radext-status-server
=09
=09

	> From: housley@vigilsec.com
	> To: iesg@ietf.org
	> CC: Francis.Dupont@fdupont.fr; radext-chairs@tools.ietf.org;
draft-ietf-radext-status-server@tools.ietf.org
	> Date: Wed, 21 Apr 2010 18:22:24 -0700
	> Subject: COMMENT: draft-ietf-radext-status-server=20
	>=20
	> Comment:
	>=20
	> Please consider the comments from the Gen-ART Review by
Francis Dupont:
	>=20
	> - Abstract page 2: there is an explicit reference to a RFC,
this is in
	> general forbidden but IMHO we are here in the allowed
exception case.
	>=20
	> - 2.1.1 page 8: a servers policy -> a server policy
	>=20
	> - 3 page 10 (twice): etc. -> etc., ???
	>=20
	> - 4.2 page 13: adminstrators -> administrators
	>=20
	> - 4.2 page 15 (twice): e.g. -> e.g.,
	>=20
	> - 4.3 page 16: modelled -> modeled
	>=20
	> - 4.3 page 16: usually the hysteresis against flapping tries
to keep
	> the connection (i.e., failover after 3 missed responses), here
it is
	> the opposite. IMHO it is very aggressive but it is how RFC
3539 works
	> so I have no concern about it.
	>=20
	> - 4.5 page 16: Proxyhas -> Proxy has
	>=20
	> - 4.5 page 17: cannot, -> cannot
	>=20
	> - 4.5 page 18: i.e. -> i.e.,
	>=20
	> - 5 page 19: EAP-MEssage -> EAP-Message
	>=20
	> - 8 page 23: synthesise -> synthesize
	>=20
	> - 8 page 23: in "the suggestion of [RFC5080] Section 2.2.2,
which suggests"
	> suggests -> proposes
	>=20
	> - 8 page 23: configurably is not in my dict?
	>=20
	> - 9.2 page 23: IMHO the RFC2119 reference should be moved to
normative
	> references section (perhaps others too?)
	>=20
	> - Authors' Addresses -> Author's Address
	>=20
=09
=09


------_=_NextPart_001_01CAE1F2.5316F534
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

<META content=3D"MSHTML 6.00.2900.5945" name=3DGENERATOR></HEAD>
<BODY class=3Dhmmessage dir=3Dltr>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010>Alan,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN =
class=3D945140208-22042010>I have not=20
seen any response from you to the issues raised in the DISCUSS and =
COMMENT made=20
by the different AD's. The IESG telechat is scheduled for today at =
11:30AM ET.=20
Are you on line and preparing answers to the issues raised? =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN =
class=3D945140208-22042010>Thanks and=20
Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010>Dan</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010></SPAN></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma><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> Thursday, April 22, 2010 4:25 AM<BR><B>To:</B>=20
  radiusext@ops.ietf.org<BR><B>Subject:</B> COMMENT:=20
  draft-ietf-radext-status-server<BR></FONT><BR></DIV>
  <DIV></DIV><BR>&gt; From: housley@vigilsec.com<BR>&gt; To:=20
  iesg@ietf.org<BR>&gt; CC: Francis.Dupont@fdupont.fr;=20
  radext-chairs@tools.ietf.org;=20
  draft-ietf-radext-status-server@tools.ietf.org<BR>&gt; Date: Wed, 21 =
Apr 2010=20
  18:22:24 -0700<BR>&gt; Subject: COMMENT: =
draft-ietf-radext-status-server=20
  <BR>&gt; <BR>&gt; Comment:<BR>&gt; <BR>&gt; Please consider the =
comments from=20
  the Gen-ART Review by Francis Dupont:<BR>&gt; <BR>&gt; - Abstract page =
2:=20
  there is an explicit reference to a RFC, this is in<BR>&gt; general =
forbidden=20
  but IMHO we are here in the allowed exception case.<BR>&gt; <BR>&gt; - =
2.1.1=20
  page 8: a servers policy -&gt; a server policy<BR>&gt; <BR>&gt; - 3 =
page 10=20
  (twice): etc. -&gt; etc., ???<BR>&gt; <BR>&gt; - 4.2 page 13: =
adminstrators=20
  -&gt; administrators<BR>&gt; <BR>&gt; - 4.2 page 15 (twice): e.g. =
-&gt;=20
  e.g.,<BR>&gt; <BR>&gt; - 4.3 page 16: modelled -&gt; modeled<BR>&gt; =
<BR>&gt;=20
  - 4.3 page 16: usually the hysteresis against flapping tries to =
keep<BR>&gt;=20
  the connection (i.e., failover after 3 missed responses), here it =
is<BR>&gt;=20
  the opposite. IMHO it is very aggressive but it is how RFC 3539 =
works<BR>&gt;=20
  so I have no concern about it.<BR>&gt; <BR>&gt; - 4.5 page 16: =
Proxyhas -&gt;=20
  Proxy has<BR>&gt; <BR>&gt; - 4.5 page 17: cannot, -&gt; cannot<BR>&gt; =

  <BR>&gt; - 4.5 page 18: i.e. -&gt; i.e.,<BR>&gt; <BR>&gt; - 5 page 19: =

  EAP-MEssage -&gt; EAP-Message<BR>&gt; <BR>&gt; - 8 page 23: synthesise =
-&gt;=20
  synthesize<BR>&gt; <BR>&gt; - 8 page 23: in "the suggestion of =
[RFC5080]=20
  Section 2.2.2, which suggests"<BR>&gt; suggests -&gt; proposes<BR>&gt; =

  <BR>&gt; - 8 page 23: configurably is not in my dict?<BR>&gt; <BR>&gt; =
- 9.2=20
  page 23: IMHO the RFC2119 reference should be moved to =
normative<BR>&gt;=20
  references section (perhaps others too?)<BR>&gt; <BR>&gt; - Authors' =
Addresses=20
  -&gt; Author's Address<BR>&gt; <BR><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAE1F2.5316F534--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 22 09:44: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 1E7723A6C0E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 22 Apr 2010 09:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.287
X-Spam-Level: 
X-Spam-Status: No, score=-1.287 tagged_above=-999 required=5 tests=[AWL=-0.792, 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 h6uKi+peprpc for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 22 Apr 2010 09:44:53 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B90C628C18E for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 22 Apr 2010 09:44:24 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O4zRe-000EAl-Lt for radiusext-data0@psg.com; Thu, 22 Apr 2010 16:40:06 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1O4zRZ-000E8g-58 for radiusext@ops.ietf.org; Thu, 22 Apr 2010 16:40:01 +0000
Received: from thor.lan (LRouen-151-71-119-225.w193-253.abo.wanadoo.fr [193.253.237.225]) by liberty.deployingradius.com (Postfix) with ESMTPSA id D991E1234490; Thu, 22 Apr 2010 18:39:58 +0200 (CEST)
Message-ID: <4BD07BEC.6070808@deployingradius.com>
Date: Thu, 22 Apr 2010 18:40:12 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, radiusext@ops.ietf.org
Subject: Re: COMMENT: draft-ietf-radext-status-server
References: <20100422012225.139A33A696D@core3.amsl.com> <BLU137-W66E08672FD489DD69AF5A93080@phx.gbl> <EDC652A26FB23C4EB6384A4584434A0402103ED0@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0402103ED0@307622ANEX5.global.avaya.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>

Romascanu, Dan (Dan) wrote:
> I have not seen any response from you to the issues raised in the
> DISCUSS and COMMENT made by the different AD's. The IESG telechat is
> scheduled for today at 11:30AM ET. Are you on line and preparing answers
> to the issues raised?

  Vacation... just responded to most, hope it's not too late.

  Alan DeKok.

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

From owner-radiusext@ops.ietf.org  Sun Apr 25 15:52: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 B63983A6934 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 25 Apr 2010 15:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.431
X-Spam-Level: *
X-Spam-Status: No, score=1.431 tagged_above=-999 required=5 tests=[AWL=-0.674, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8BiTlE3pjOa for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 25 Apr 2010 15:52:49 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5A86A3A6816 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 25 Apr 2010 15:52:48 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6Ads-000GwA-1S for radiusext-data0@psg.com; Sun, 25 Apr 2010 22:49:36 +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 1O6Adp-000Gva-8Q for radiusext@ops.ietf.org; Sun, 25 Apr 2010 22:49:33 +0000
Received: from BLU137-DS3 ([65.55.116.7]) by blu0-omc1-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 25 Apr 2010 15:49:32 -0700
X-Originating-IP: [68.178.109.243]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS346EDD650AB6D0393D2AB93050@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Stefan Winter'" <mail@stefan-winter.de>
CC: <radiusext@ops.ietf.org>
References: <BLU137-W194A6A55C396F3F124BE81932A0@phx.gbl> <4BCD93B9.6030807@stefan-winter.de>
In-Reply-To: <4BCD93B9.6030807@stefan-winter.de>
Subject: RE: RADEXT WG Last Call on "TLS Encryption for RADIUS" (Experimental)
Date: Sun, 25 Apr 2010 15:49:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acrgfuefb9xGl/YsSY6SxYOksHnG9wESck5g
Content-Language: en-us
X-OriginalArrivalTime: 25 Apr 2010 22:49:32.0247 (UTC) FILETIME=[91FF5670:01CAE4C9]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

I am starting work on a PROTO writeup for this document, on the assumption
that "lack of response implies consent".  If any issues become apparent 
in the course of that review, I'll post them to the list. 

While that's in progress,  WG participants are encouraged to:

a. Read the document, and post any thoughts to the list (even if that is
only
"the document appears ready"); 
b. Continue to make progress on closing issues within dependency documents 
(e.g. RADIUS over TCP, Status-Server); 
c. Post updates on implementation progress; 

Thanks for your efforts on this document!

-----Original Message-----
From: Stefan Winter [mailto:mail@stefan-winter.de] 
Sent: Tuesday, April 20, 2010 4:45 AM
To: Bernard Aboba
Subject: Re: RADEXT WG Last Call on "TLS Encryption for RADIUS"
(Experimental)

Hi,

so...? Is the absence of comments enough to justify going on to IETF LC?
Would be much appreciated :-)

Stefan

Am 19.03.2010 20:59, schrieb Bernard Aboba:
> This is an announcement of RADEXT WG last call on "TLS Encryption for
> RADIUS", prior to sending the document to the IESG for publication as
> an Experimental RFC.
>
> The document is available for inspection here:
> http://tools.ietf.org/html/draft-ietf-radext-radsec
>
> The RADEXT WG last call will last until April 19, 2010.   If you have
> comments on the document, please send them to the RADEXT WG mailing
> list (radiusext@ops.ietf.org) in the format described on the RADEXT
> Issues list (http://www.drizzle.com/~aboba/RADEXT/ ). 



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

From owner-radiusext@ops.ietf.org  Sun Apr 25 16:22:12 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DFE4E3A68C1 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 25 Apr 2010 16:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.444
X-Spam-Level: *
X-Spam-Status: No, score=1.444 tagged_above=-999 required=5 tests=[AWL=-0.662, 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 DgTguuUTy4v5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 25 Apr 2010 16:22:10 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 2FB913A6A03 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 25 Apr 2010 16:21:59 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6B4X-000LtQ-PR for radiusext-data0@psg.com; Sun, 25 Apr 2010 23:17:09 +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 1O6B4U-000Lt6-Kd for radiusext@ops.ietf.org; Sun, 25 Apr 2010 23:17:06 +0000
Received: from BLU137-W20 ([65.55.116.7]) by blu0-omc1-s10.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 25 Apr 2010 16:17:05 -0700
Message-ID: <BLU137-W20CFFD1E4C3104581A412393050@phx.gbl>
Content-Type: multipart/alternative; boundary="_9fc0c086-7c07-4180-a53f-e4f9cbdd5486_"
X-Originating-IP: [68.178.109.243]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Bernard's notes
Date: Sun, 25 Apr 2010 16:17:05 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 25 Apr 2010 23:17:05.0785 (UTC) FILETIME=[6B953690:01CAE4CD]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_9fc0c086-7c07-4180-a53f-e4f9cbdd5486_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Just a note to the WG to summarize where I think we are on various work ite=
ms.  The hope is that this note will disclose any disconnects which could l=
ead to things falling through the cracks.=20

Issue List (recently updated): http://www.drizzle.com/~aboba/RADEXT/

1. Completed IESG Review: Revision Needed

My notes show two documents in this category:  Design Guidelines and Status=
 Server.  In both cases=2C it appears to me that the editor (Alan DeKok) is=
 holding the token.

Design Guidelines

This document currently has no open IESG DISCUSSes.=20

With respect to Design Guidelines=2C we have two issues in the Pending stat=
e:  325 and 327.  Alan has updated the draft to -13=2C and has posted a req=
uest for review of the changes to address both issues.  There is a discussi=
on of Issue 327 in progress.  In the absence of further discussion on Issue=
 325=2C we are going to assume that it has been resolved.=20

Next steps: WG participants are requested to review the Design Guidelines d=
ocument and post their thoughts to the list:
http://tools.ietf.org/html/draft-ietf-radext-design

Status Server

This document currently has IESG DISCUSS comments open (see Issue #333)=2C =
in addition to IETF last call comments (Issue # 330). =20

Next steps:  The editor need to address the open issues=2C preferably by po=
sting a document revision. =20

2. AD Review:  Revision Needed

My notes show one document in this category:  RADIUS over TCP=2C with the e=
ditor (Alan DeKok) holding the token..=20

There are two open issues relating to the Dan's AD review:  Issues 331 (tec=
hnical) and 332 (editorial). =20

Next steps:  The editor needs to address the open issues=2C preferably by p=
osting a document revision.=20

3. Completed RADEXT WG Last Call: Pending PROTO Writeup

My notes show one document in this category:  Tunnel Type Values=2C with Da=
ve Nelson holding the token.=20

In the past=2C there had been some discussion about whether RFC 3575 intend=
ed to change the IANA allocation process for Tunnel-Type values to "expert =
review"=2C even though it did not include RFC 2868 in the Updates: header. =
  If so=2C could an errata if approved make this document unnecessary (give=
n that an expert review has already been done)? =20

Next steps:  Dave Nelson to complete the PROTO writeup.=20

4. Completed RADEXT WG last call: Revision needed.

My notes show one document in this category:  IPv6 Access. =20

There is one issue outstanding from the RADEXT WG last call:  Issue #335.=20

Next steps:  The editor needs to address the open issues=2C preferably by=20
posting a document revision.=20

5. Completed RADEXT WG last call:  PROTO writeup.=20

My notes show one document in this category:  RADIUS over TLS.=20

There are no outstanding issues from RADEXT WG last call.=20

Next steps:  Bernard Aboba to complete PROTO writeup=3B RADEXT WG participa=
nts to read the document and post comments to the list.=20






 		 	   		  =

--_9fc0c086-7c07-4180-a53f-e4f9cbdd5486_
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'>
Just a note to the WG to summarize where I think we are on various work ite=
ms.&nbsp=3B The hope is that this note will disclose any disconnects which =
could lead to things falling through the cracks. <br><br>Issue List (recent=
ly updated): http://www.drizzle.com/~aboba/RADEXT/<br><br>1. Completed IESG=
 Review: Revision Needed<br><br>My notes show two documents in this categor=
y:&nbsp=3B Design Guidelines and Status Server.&nbsp=3B In both cases=2C it=
 appears to me that the editor (Alan DeKok) is holding the token.<br><br>De=
sign Guidelines<br><br>This document currently has no open IESG DISCUSSes. =
<br><br>With respect to Design Guidelines=2C we have two issues in the Pend=
ing state:&nbsp=3B 325 and 327.&nbsp=3B Alan has updated the draft to -13=
=2C and has posted a request for review of the changes to address both issu=
es.&nbsp=3B There is a discussion of Issue 327 in progress.&nbsp=3B In the =
absence of further discussion on Issue 325=2C we are going to assume that i=
t has been resolved. <br><br>Next steps: WG participants are requested to r=
eview the Design Guidelines document and post their thoughts to the list:<b=
r>http://tools.ietf.org/html/draft-ietf-radext-design<br><br>Status Server<=
br><br>This document currently has IESG DISCUSS comments open (see Issue #3=
33)=2C in addition to IETF last call comments (Issue # 330).&nbsp=3B <br><b=
r>Next steps:&nbsp=3B The editor need to address the open issues=2C prefera=
bly by posting a document revision.&nbsp=3B <br><br>2. AD Review:&nbsp=3B R=
evision Needed<br><br>My notes show one document in this category:&nbsp=3B =
RADIUS over TCP=2C with the editor (Alan DeKok) holding the token.. <br><br=
>There are two open issues relating to the Dan's AD review:&nbsp=3B Issues =
331 (technical) and 332 (editorial).&nbsp=3B <br><br>Next steps:&nbsp=3B Th=
e editor needs to address the open issues=2C preferably by posting a docume=
nt revision. <br><br>3. Completed RADEXT WG Last Call: Pending PROTO Writeu=
p<br><br>My notes show one document in this category:&nbsp=3B Tunnel Type V=
alues=2C with Dave Nelson holding the token. <br><br>In the past=2C there h=
ad been some discussion about whether RFC 3575 intended to change the IANA =
allocation process for Tunnel-Type values to "expert review"=2C even though=
 it did not include RFC 2868 in the Updates: header.&nbsp=3B&nbsp=3B If so=
=2C could an errata if approved make this document unnecessary (given that =
an expert review has already been done)?&nbsp=3B <br><br>Next steps:&nbsp=
=3B Dave Nelson to complete the PROTO writeup. <br><br>4. Completed RADEXT =
WG last call: Revision needed.<br><br>My notes show one document in this ca=
tegory:&nbsp=3B IPv6 Access.&nbsp=3B <br><br>There is one issue outstanding=
 from the RADEXT WG last call:&nbsp=3B Issue #335. <br><br>Next steps:&nbsp=
=3B The editor needs to address the open issues=2C preferably by=20
posting a document revision. <br><br>5. Completed RADEXT WG last call:&nbsp=
=3B PROTO writeup. <br><br>My notes show one document in this category:&nbs=
p=3B RADIUS over TLS. <br><br>There are no outstanding issues from RADEXT W=
G last call. <br><br>Next steps:&nbsp=3B Bernard Aboba to complete PROTO wr=
iteup=3B RADEXT WG participants to read the document and post comments to t=
he list. <br><br><br><br><br><br><br> 		 	   		  </body>
</html>=

--_9fc0c086-7c07-4180-a53f-e4f9cbdd5486_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 26 01:32: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 7D9643A696F for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 01:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.08
X-Spam-Level: 
X-Spam-Status: No, score=0.08 tagged_above=-999 required=5 tests=[AWL=-2.026, 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 lo8jkEYXDK+M for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 01:32:38 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 796333A68FA for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 26 Apr 2010 01:32:22 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6Je8-000Mj5-8A for radiusext-data0@psg.com; Mon, 26 Apr 2010 08:26:28 +0000
Received: from [135.11.29.16] (helo=p-us1-iereast-outbound-tmp.us1.avaya.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <dromasca@avaya.com>) id 1O6Je2-000MiS-G8 for radiusext@ops.ietf.org; Mon, 26 Apr 2010 08:26:22 +0000
X-IronPort-AV: E=Sophos;i="4.52,272,1270440000";  d="scan'208,217";a="13149726"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 26 Apr 2010 04:26:15 -0400
X-IronPort-AV: E=Sophos;i="4.52,272,1270440000";  d="scan'208,217";a="454881417"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 26 Apr 2010 04:25:40 -0400
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAE51A.0435A9B3"
Subject: RE: Bernard's notes
Date: Mon, 26 Apr 2010 10:25:22 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402144E5D@307622ANEX5.global.avaya.com>
In-Reply-To: <BLU137-W20CFFD1E4C3104581A412393050@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bernard's notes
Thread-Index: AcrkzbWA2ElDKIglRqKoNvDNBKDqcAAS1KmQ
References: <BLU137-W20CFFD1E4C3104581A412393050@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_01CAE51A.0435A9B3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Bernard,
=20
Thank you for your status notes. I have two comments:=20
=20
1. Design guidelines - you mention that there are no open IESG DISCUSSes
- this is true, but we should not forget that as discussed previously
because of the rather extensive changes we will need to redo the IESG LC
(may be shorter than the usual four weeks) and redo also the IESG
ballot.=20
=20
2. Alan is holding the pen as editor for all three documents at #1 and
#2. Thanks Alan for doing this - however the chairs may want to consider
a more efficient sharing of the editorial load between the different key
contributors in the future.=20
=20
Dan
=20


________________________________

	From: owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
	Sent: Monday, April 26, 2010 2:17 AM
	To: radiusext@ops.ietf.org
	Subject: Bernard's notes
=09
=09
	Just a note to the WG to summarize where I think we are on
various work items.  The hope is that this note will disclose any
disconnects which could lead to things falling through the cracks.=20
=09
	Issue List (recently updated):
http://www.drizzle.com/~aboba/RADEXT/
=09
	1. Completed IESG Review: Revision Needed
=09
	My notes show two documents in this category:  Design Guidelines
and Status Server.  In both cases, it appears to me that the editor
(Alan DeKok) is holding the token.
=09
	Design Guidelines
=09
	This document currently has no open IESG DISCUSSes.=20
=09
	With respect to Design Guidelines, we have two issues in the
Pending state:  325 and 327.  Alan has updated the draft to -13, and has
posted a request for review of the changes to address both issues.
There is a discussion of Issue 327 in progress.  In the absence of
further discussion on Issue 325, we are going to assume that it has been
resolved.=20
=09
	Next steps: WG participants are requested to review the Design
Guidelines document and post their thoughts to the list:
	http://tools.ietf.org/html/draft-ietf-radext-design
=09
	Status Server
=09
	This document currently has IESG DISCUSS comments open (see
Issue #333), in addition to IETF last call comments (Issue # 330). =20
=09
	Next steps:  The editor need to address the open issues,
preferably by posting a document revision. =20
=09
	2. AD Review:  Revision Needed
=09
	My notes show one document in this category:  RADIUS over TCP,
with the editor (Alan DeKok) holding the token..=20
=09
	There are two open issues relating to the Dan's AD review:
Issues 331 (technical) and 332 (editorial). =20
=09
	Next steps:  The editor needs to address the open issues,
preferably by posting a document revision.=20
=09
	3. Completed RADEXT WG Last Call: Pending PROTO Writeup
=09
	My notes show one document in this category:  Tunnel Type
Values, with Dave Nelson holding the token.=20
=09
	In the past, there had been some discussion about whether RFC
3575 intended to change the IANA allocation process for Tunnel-Type
values to "expert review", even though it did not include RFC 2868 in
the Updates: header.   If so, could an errata if approved make this
document unnecessary (given that an expert review has already been
done)? =20
=09
	Next steps:  Dave Nelson to complete the PROTO writeup.=20
=09
	4. Completed RADEXT WG last call: Revision needed.
=09
	My notes show one document in this category:  IPv6 Access. =20
=09
	There is one issue outstanding from the RADEXT WG last call:
Issue #335.=20
=09
	Next steps:  The editor needs to address the open issues,
preferably by posting a document revision.=20
=09
	5. Completed RADEXT WG last call:  PROTO writeup.=20
=09
	My notes show one document in this category:  RADIUS over TLS.=20
=09
	There are no outstanding issues from RADEXT WG last call.=20
=09
	Next steps:  Bernard Aboba to complete PROTO writeup; RADEXT WG
participants to read the document and post comments to the list.=20
=09
=09
=09
=09
=09
=09
=09


------_=_NextPart_001_01CAE51A.0435A9B3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<META content=3D"MSHTML 6.00.2900.5945" name=3DGENERATOR></HEAD>
<BODY class=3Dhmmessage>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff>Bernard,</FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial =
color=3D#0000ff>Thank you for=20
your status notes. I have two comments: </FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial =
color=3D#0000ff>1. Design=20
guidelines - you mention that there are no open IESG DISCUSSes - this is =
true,=20
but we should not forget that as discussed previously&nbsp;because of =
the rather=20
extensive changes we will need to redo the IESG LC (may be shorter than =
the=20
usual four weeks) and redo also the IESG ballot. </FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial =
color=3D#0000ff>2. Alan is=20
holding the pen as editor for all three documents at #1 and #2. Thanks =
Alan for=20
doing this -&nbsp;however the chairs may want to consider a more =
efficient=20
sharing of the editorial load between the different key contributors in =
the=20
future. </FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff>Dan</FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma><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> Monday, April 26, 2010 2:17 AM<BR><B>To:</B>=20
  radiusext@ops.ietf.org<BR><B>Subject:</B> Bernard's =
notes<BR></FONT><BR></DIV>
  <DIV></DIV>Just a note to the WG to summarize where I think we are on =
various=20
  work items.&nbsp; The hope is that this note will disclose any =
disconnects=20
  which could lead to things falling through the cracks. <BR><BR>Issue =
List=20
  (recently updated): http://www.drizzle.com/~aboba/RADEXT/<BR><BR>1. =
Completed=20
  IESG Review: Revision Needed<BR><BR>My notes show two documents in =
this=20
  category:&nbsp; Design Guidelines and Status Server.&nbsp; In both =
cases, it=20
  appears to me that the editor (Alan DeKok) is holding the =
token.<BR><BR>Design=20
  Guidelines<BR><BR>This document currently has no open IESG DISCUSSes.=20
  <BR><BR>With respect to Design Guidelines, we have two issues in the =
Pending=20
  state:&nbsp; 325 and 327.&nbsp; Alan has updated the draft to -13, and =
has=20
  posted a request for review of the changes to address both =
issues.&nbsp; There=20
  is a discussion of Issue 327 in progress.&nbsp; In the absence of =
further=20
  discussion on Issue 325, we are going to assume that it has been =
resolved.=20
  <BR><BR>Next steps: WG participants are requested to review the Design =

  Guidelines document and post their thoughts to the=20
  =
list:<BR>http://tools.ietf.org/html/draft-ietf-radext-design<BR><BR>Statu=
s=20
  Server<BR><BR>This document currently has IESG DISCUSS comments open =
(see=20
  Issue #333), in addition to IETF last call comments (Issue # =
330).&nbsp;=20
  <BR><BR>Next steps:&nbsp; The editor need to address the open issues,=20
  preferably by posting a document revision.&nbsp; <BR><BR>2. AD =
Review:&nbsp;=20
  Revision Needed<BR><BR>My notes show one document in this =
category:&nbsp;=20
  RADIUS over TCP, with the editor (Alan DeKok) holding the token..=20
  <BR><BR>There are two open issues relating to the Dan's AD =
review:&nbsp;=20
  Issues 331 (technical) and 332 (editorial).&nbsp; <BR><BR>Next =
steps:&nbsp;=20
  The editor needs to address the open issues, preferably by posting a =
document=20
  revision. <BR><BR>3. Completed RADEXT WG Last Call: Pending PROTO=20
  Writeup<BR><BR>My notes show one document in this category:&nbsp; =
Tunnel Type=20
  Values, with Dave Nelson holding the token. <BR><BR>In the past, there =
had=20
  been some discussion about whether RFC 3575 intended to change the =
IANA=20
  allocation process for Tunnel-Type values to "expert review", even =
though it=20
  did not include RFC 2868 in the Updates: header.&nbsp;&nbsp; If so, =
could an=20
  errata if approved make this document unnecessary (given that an =
expert review=20
  has already been done)?&nbsp; <BR><BR>Next steps:&nbsp; Dave Nelson to =

  complete the PROTO writeup. <BR><BR>4. Completed RADEXT WG last call: =
Revision=20
  needed.<BR><BR>My notes show one document in this category:&nbsp; IPv6 =

  Access.&nbsp; <BR><BR>There is one issue outstanding from the RADEXT =
WG last=20
  call:&nbsp; Issue #335. <BR><BR>Next steps:&nbsp; The editor needs to =
address=20
  the open issues, preferably by posting a document revision. <BR><BR>5. =

  Completed RADEXT WG last call:&nbsp; PROTO writeup. <BR><BR>My notes =
show one=20
  document in this category:&nbsp; RADIUS over TLS. <BR><BR>There are no =

  outstanding issues from RADEXT WG last call. <BR><BR>Next steps:&nbsp; =
Bernard=20
  Aboba to complete PROTO writeup; RADEXT WG participants to read the =
document=20
  and post comments to the list.=20
<BR><BR><BR><BR><BR><BR><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAE51A.0435A9B3--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 26 03:51: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 CC5853A68FE for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 03:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.595
X-Spam-Level: 
X-Spam-Status: No, score=-7.595 tagged_above=-999 required=5 tests=[AWL=-1.700, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIx-VR6hNhtS for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 03:51:56 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 65B773A68D5 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 26 Apr 2010 03:51:55 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6Lra-000161-85 for radiusext-data0@psg.com; Mon, 26 Apr 2010 10:48:30 +0000
Received: from [144.254.224.140] (helo=ams-iport-1.cisco.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <wdec@cisco.com>) id 1O6LrX-00015T-4g for radiusext@ops.ietf.org; Mon, 26 Apr 2010 10:48:27 +0000
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkoBAAMM1UuQ/uCWiWdsb2JhbACcNxUBAQEKCxERBhymLJk4hQwE
X-IronPort-AV: E=Sophos;i="4.52,272,1270425600";  d="scan'208";a="60066934"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 26 Apr 2010 10:48:25 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o3QAmPPj001141; Mon, 26 Apr 2010 10:48:25 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 26 Apr 2010 12:48:24 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Date: Mon, 26 Apr 2010 12:48:24 +0200
Message-ID: <A16B9A4922C4A544A94565E870362B5001C5D034@XMB-AMS-111.cisco.com>
In-Reply-To: <alpine.WNT.2.00.1003031205030.2788@littlesmurf>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Thread-Index: Acq7Dr64kyHowWg8Q7CO9Gzt/0sSEAqHeqnw
References: <BLU137-DS10984B808F980DCD000E11933C0@phx.gbl> <alpine.WNT.2.00.1003011200180.2316@SMURF> <BLU137-DS37F6470B23B0440097973933C0@phx.gbl> <alpine.WNT.2.00.1003011339340.2788@littlesmurf> <A16B9A4922C4A544A94565E870362B50015A219E@XMB-AMS-111.cisco.com> <alpine.WNT.2.00.1003020450400.2316@SMURF> <A16B9A4922C4A544A94565E870362B50015A2469@XMB-AMS-111.cisco.com> <alpine.WNT.2.00.1003021143010.2316@SMURF> <A16B9A4922C4A544A94565E870362B50015A269D@XMB-AMS-111.cisco.com> <alpine.WNT.2.00.1003031205030.2788@littlesmurf>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Peter Deacon" <peterd@iea-software.com>
Cc: <radiusext@ops.ietf.org>
X-OriginalArrivalTime: 26 Apr 2010 10:48:24.0989 (UTC) FILETIME=[FF1D74D0:01CAE52D]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hello Peter,

As part of the resolution of Issue 335, we're proposing the addition of
the following text/section into the draft. Please let us know if this is
satisfactory.

"Syntactically, the Framed-IPv6-Address and the RFC3162
Framed-IPv6-Prefix attributes are identical. In terms of their intended
semantics however the former represents a statefully assigned IPv6
address while the latter a prefix intended for application on a target
interface and are envisaged to be used in co-existence. Thus, in order
to preserve this semantical distinction it is recommended that each
attribute be used for its intended purpose, with the functional
substitution of one attribute for the other being an optional
configuration feature of a Radius client."

Thanks,
Woj.



> -----Original Message-----
> From: Peter Deacon [mailto:peterd@iea-software.com]
> Sent: 03 March 2010 21:19
> To: Wojciech Dec (wdec)
> Cc: radiusext@ops.ietf.org
> Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access
> Networks
>=20
> On Wed, 3 Mar 2010, Wojciech Dec (wdec) wrote:
>=20
> >> My suggestion WRT an accounting restriction is based on a scenario:
> >> Accounting system relies on RFC 3162 to report client IP.
>=20
> >> NAS decides to send IPv6-Framed-Address rather than RFC 3162
method.
> >> Accounting system requires modification to continue to
> >> understand the same information.
>=20
> > Yes, I see your point. Don't you think however that this could be
> > handled by a client knob/implementation? I.E. If in an access-accept
> a
> > server sends the IPv6-Framed-Address, then the NAS client can
> interpret
> > it to mean that its ok to use this attribute in accounting messages.
> If
>=20
> > an IPv6-Framed-Address does not come down in an access-accept, then
> the
> > NAS would use by default "whatever it uses today", unless it has
been
> > explicitly configured to send accounting info with using
> > IPv6-Framed-Address.
>=20
> > This would seem to cover your concerns. What do you think?
>=20
> Yes, sounds reasonable.
>=20
> regards,
> Peter

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

From owner-radiusext@ops.ietf.org  Mon Apr 26 10:07: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 DB61028C1FD for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 10:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.325
X-Spam-Level: *
X-Spam-Status: No, score=1.325 tagged_above=-999 required=5 tests=[AWL=-0.780, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqOXb2t8Md6o for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 10:07:12 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8293028C21C for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 26 Apr 2010 10:01:40 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6Rb3-000AlH-Af for radiusext-data0@psg.com; Mon, 26 Apr 2010 16:55:49 +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 1O6Rax-000Ahy-Pp for radiusext@ops.ietf.org; Mon, 26 Apr 2010 16:55:44 +0000
Message-ID: <4BD5C58D.6040303@deployingradius.com>
Date: Mon, 26 Apr 2010 18:55:41 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
CC: radiusext@ops.ietf.org
Subject: Re: AD review of draft-ietf-radext-tcp-transport-05
References: <EDC652A26FB23C4EB6384A4584434A0401FFEFAC@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401FFEFAC@307622ANEX5.global.avaya.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>

Romascanu, Dan (Dan) wrote:
> The issues are divided into Technical (T) and Editorial (E). 
> 
> T1. The document is marked as EXPERIMENTAL. It would be useful if it
> mentions in one of the introductory sections what are the goals and
> limitations (if any) of the experimental deployment and what would be
> the success criteria of the experiment that would allow for taking the
> document to the standards track later. 

  Suggested text for Section 1 (Introduction).  Move the last paragraph
from Section 1.2 to higher up in the document, and add some text:

...
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 additional
confidentiality and security) is NOT RECOMMENDED, as there has been
little or no operational experience with it.

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

> T2. Section 2.2: 
> 
>>  Since these ports are unused by existing RADIUS implementations, the
>    assigned values SHOULD be used as the default ports for RADIUS over
>    TCP.
> 
> Why is this a SHOULD and not a MUST? 

  No reason...  I'll change it.

> T3. Section 2.3 needs a complete re-writing: 
...
> The correct solution is for the MIB documents to be updated in the
> future with new MIB objects of appropriate syntax. For the time being
> the only thing that this section should say is that the MIB modules do
> not support RADIUS over TCP and that they will need to be updated in the
> future. 

  Suggest replacing the text in 2.3 with:

The MIB Module definitions in [RFC4668], [RFC4669], [RFC4670],
[RFC4671], [RFC4672], and [RFC4673] are intended to be used for RADIUS
over UDP.  As such, they do not support RADIUS over TCP, and will need
to be updated in the future.  Implementations of RADIUS over TCP
SHOULD NOT re-use these MIB Modules to perform statistics counting for
RADIUS over TCP connections.

> T4. The following section in 2.6.1 is confusing: 
> 
>>  Much of the discussion in this section can be summarized by the
>    following requirement.  RADIUS requests MAY be re-transmitted
>    verbatim only if the following 5-tuple (Client IP address, Client
>    port, Transport Protocol, Server IP address, Server port) remains the
>    same. 

  I think it's best to simply delete that paragraph.

> T5. The last paragraph in 2.6.1: 
> 
>>   The above requirement is necessary, but not sufficient in all cases.
>    Other specifications give additional situations where the packet is
>    to be considered as a new request.  Those recommendations MUST also
>    be followed.
> 
> Having a MUST requirement over undefined 'other specification' is not
> implementable. I would suggest to either clarify what are these 'other
> specifications' or take this out. 

  OK.  I'll delete it.

> E1. Please expand TLS at first occurrence. 

  Done.

> E2. The Introduction section speaks about 'the default Internet MTU
> (576). Strictly speaking this value is not standardized in any place,

  That should be the "common Internet MTU".  The text could say:

These packets are larger than the common
Internet MTU (576), resulting in fragmentation of the packets at the
IP layer when they are proxied over the Internet.

> and later in section 1.1 reference is made to RADIUS packets being
> restricted to 1500 octets in size. Looks like an unnecessary
> inconsistency. 

  That is for a different use-case.  I can update that text to say:

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 the common Ethernet MTU (1500 octets) for EAP over
LAN (EAPoL) use-cases.

> E3. Section 1.2 - the syntax in the RADIUS server definition is
> inconsistent with the syntax of the rest of the definitions

  OK.  That could say:

A device that provides one or more of authentication, authorization,
and/or accounting (AAA) services to a NAS.


> E4. Section 2.6.7: 
> 
>>  We RECOMMEND that implementors of this specification
>    familiarize themselves with TCP application programming concepts.  We
>    RECOMMEND also that existing TCP applications be examined with an eye
>    to robustness, performance, scalability, etc.
> 
> The use of capitalized (a la 2119) keywords in a personalized phrase
> does not make much sense. RECOMMEND is not a keyword actually. I suggest
> rephrasing. 

  Changed to: "It is RECOMMENDED that..."

  If this looks OK, I'll issue an updated draft tomorrow.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 26 10:40:42 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F4583A6AA4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 10:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.364
X-Spam-Level: *
X-Spam-Status: No, score=1.364 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vwfPwNSO5zqk for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 10:40:41 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 16AEA3A695F for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 26 Apr 2010 10:40:41 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6SFw-000Jqh-9C for radiusext-data0@psg.com; Mon, 26 Apr 2010 17:38:04 +0000
Received: from [70.89.142.196] (helo=aspen.internal.iea-software.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <peterd@iea-software.com>) id 1O6SFs-000JpM-6k for radiusext@ops.ietf.org; Mon, 26 Apr 2010 17:38:00 +0000
Received: from SMURF (unverified [10.0.3.195]) by aspen.internal.iea-software.com (Rockliffe SMTPRA 7.0.6) with ESMTP id <B0005284466@aspen.internal.iea-software.com>; Mon, 26 Apr 2010 10:37:57 -0700
Date: Mon, 26 Apr 2010 10:37:56 -0700 (Pacific Daylight Time)
From: Peter Deacon <peterd@iea-software.com>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>
cc: radiusext@ops.ietf.org
Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
In-Reply-To: <A16B9A4922C4A544A94565E870362B5001C5D034@XMB-AMS-111.cisco.com>
Message-ID: <alpine.WNT.2.00.1004260932320.2388@SMURF>
References: <BLU137-DS10984B808F980DCD000E11933C0@phx.gbl> <alpine.WNT.2.00.1003011200180.2316@SMURF> <BLU137-DS37F6470B23B0440097973933C0@phx.gbl> <alpine.WNT.2.00.1003011339340.2788@littlesmurf> <A16B9A4922C4A544A94565E870362B50015A219E@XMB-AMS-111.cisco.com> <alpine.WNT.2.00.1003020450400.2316@SMURF> <A16B9A4922C4A544A94565E870362B50015A2469@XMB-AMS-111.cisco.com> <alpine.WNT.2.00.1003021143010.2316@SMURF> <A16B9A4922C4A544A94565E870362B50015A269D@XMB-AMS-111.cisco.com> <alpine.WNT.2.00.1003031205030.2788@littlesmurf> <A16B9A4922C4A544A94565E870362B5001C5D034@XMB-AMS-111.cisco.com>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On Mon, 26 Apr 2010, Wojciech Dec (wdec) wrote:

> Hello Peter,
> As part of the resolution of Issue 335, we're proposing the addition of
> the following text/section into the draft. Please let us know if this is
> satisfactory.

> "Syntactically, the Framed-IPv6-Address and the RFC3162
> Framed-IPv6-Prefix attributes are identical. In terms of their intended
> semantics however the former represents a statefully assigned IPv6
> address while the latter a prefix intended for application on a target
> interface and are envisaged to be used in co-existence. Thus, in order
> to preserve this semantical distinction it is recommended that each
> attribute be used for its intended purpose, with the functional
> substitution of one attribute for the other being an optional
> configuration feature of a Radius client."

Hi Woj,

For Accounting messages in only the narrow case where Framed-IPv6-Address 
is assigned and no prefix is ultimatly allocated to the user what do you 
think about a recommendation for the /128 prefix be sent as well?

Regardless your text works for me as-is, thank you.

regards,
Peter

> Thanks,
> Woj.

>> -----Original Message-----
>> From: Peter Deacon [mailto:peterd@iea-software.com]
>> Sent: 03 March 2010 21:19
>> To: Wojciech Dec (wdec)
>> Cc: radiusext@ops.ietf.org
>> Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access
>> Networks
>>
>> On Wed, 3 Mar 2010, Wojciech Dec (wdec) wrote:
>>
>>>> My suggestion WRT an accounting restriction is based on a scenario:
>>>> Accounting system relies on RFC 3162 to report client IP.
>>
>>>> NAS decides to send IPv6-Framed-Address rather than RFC 3162
> method.
>>>> Accounting system requires modification to continue to
>>>> understand the same information.
>>
>>> Yes, I see your point. Don't you think however that this could be
>>> handled by a client knob/implementation? I.E. If in an access-accept
>> a
>>> server sends the IPv6-Framed-Address, then the NAS client can
>> interpret
>>> it to mean that its ok to use this attribute in accounting messages.
>> If
>>
>>> an IPv6-Framed-Address does not come down in an access-accept, then
>> the
>>> NAS would use by default "whatever it uses today", unless it has
> been
>>> explicitly configured to send accounting info with using
>>> IPv6-Framed-Address.
>>
>>> This would seem to cover your concerns. What do you think?
>>
>> Yes, sounds reasonable.
>>
>> regards,
>> Peter
>

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

From owner-radiusext@ops.ietf.org  Mon Apr 26 10:51: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 58E0E28C1D6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 10:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.367
X-Spam-Level: 
X-Spam-Status: No, score=-8.367 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxeZkzkWrUrB for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 10:51:40 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 9F07D28C1F0 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 26 Apr 2010 10:51:24 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6SQY-000MKk-Hq for radiusext-data0@psg.com; Mon, 26 Apr 2010 17:49:02 +0000
Received: from [171.71.176.72] (helo=sj-iport-3.cisco.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <wdec@cisco.com>) id 1O6SQV-000MKO-Nt for radiusext@ops.ietf.org; Mon, 26 Apr 2010 17:48:59 +0000
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAOtu1UurR7Hu/2dsb2JhbACcPnGpaJoAhQsE
X-IronPort-AV: E=Sophos;i="4.52,274,1270425600";  d="scan'208";a="220401889"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 26 Apr 2010 17:48:59 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o3QHmwnA014246; Mon, 26 Apr 2010 17:48:58 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); Mon, 26 Apr 2010 19:48:57 +0200
Received: from 10.55.215.36 ([10.55.215.36]) by XMB-AMS-111.cisco.com ([144.254.74.86]) with Microsoft Exchange Server HTTP-DAV ; Mon, 26 Apr 2010 17:48:57 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 26 Apr 2010 19:49:00 +0200
Subject: Re: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
From: Wojciech Dec <wdec@cisco.com>
To: Peter Deacon <peterd@iea-software.com>
CC: <radiusext@ops.ietf.org>
Message-ID: <C7FB9EAC.33CF%wdec@cisco.com>
Thread-Topic: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Thread-Index: AcrlaMBacINmIXU5aUGJvRf7FcLf+w==
In-Reply-To: <alpine.WNT.2.00.1004260932320.2388@SMURF>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 26 Apr 2010 17:48:57.0774 (UTC) FILETIME=[BF06E4E0:01CAE568]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hello Peter,


On 26/04/2010 19:37, "Peter Deacon" <peterd@iea-software.com> wrote:

> On Mon, 26 Apr 2010, Wojciech Dec (wdec) wrote:
> 
>> Hello Peter,
>> As part of the resolution of Issue 335, we're proposing the addition of
>> the following text/section into the draft. Please let us know if this is
>> satisfactory.
> 
>> "Syntactically, the Framed-IPv6-Address and the RFC3162
>> Framed-IPv6-Prefix attributes are identical. In terms of their intended
>> semantics however the former represents a statefully assigned IPv6
>> address while the latter a prefix intended for application on a target
>> interface and are envisaged to be used in co-existence. Thus, in order
>> to preserve this semantical distinction it is recommended that each
>> attribute be used for its intended purpose, with the functional
>> substitution of one attribute for the other being an optional
>> configuration feature of a Radius client."
> 
> Hi Woj,
> 
> For Accounting messages in only the narrow case where Framed-IPv6-Address
> is assigned and no prefix is ultimatly allocated to the user what do you
> think about a recommendation for the /128 prefix be sent as well?

Yes, I would expect this to be already captured in the attribute usage
section/table with the 0+ notation. It's my understanding that the inclusion
of such optional Radius attributes is always made configurable.

> 
> Regardless your text works for me as-is, thank you.
>
Thanks,
Woj. 
> regards,
> Peter
> 
>> Thanks,
>> Woj.
> 
>>> -----Original Message-----
>>> From: Peter Deacon [mailto:peterd@iea-software.com]
>>> Sent: 03 March 2010 21:19
>>> To: Wojciech Dec (wdec)
>>> Cc: radiusext@ops.ietf.org
>>> Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access
>>> Networks
>>> 
>>> On Wed, 3 Mar 2010, Wojciech Dec (wdec) wrote:
>>> 
>>>>> My suggestion WRT an accounting restriction is based on a scenario:
>>>>> Accounting system relies on RFC 3162 to report client IP.
>>> 
>>>>> NAS decides to send IPv6-Framed-Address rather than RFC 3162
>> method.
>>>>> Accounting system requires modification to continue to
>>>>> understand the same information.
>>> 
>>>> Yes, I see your point. Don't you think however that this could be
>>>> handled by a client knob/implementation? I.E. If in an access-accept
>>> a
>>>> server sends the IPv6-Framed-Address, then the NAS client can
>>> interpret
>>>> it to mean that its ok to use this attribute in accounting messages.
>>> If
>>> 
>>>> an IPv6-Framed-Address does not come down in an access-accept, then
>>> the
>>>> NAS would use by default "whatever it uses today", unless it has
>> been
>>>> explicitly configured to send accounting info with using
>>>> IPv6-Framed-Address.
>>> 
>>>> This would seem to cover your concerns. What do you think?
>>> 
>>> Yes, sounds reasonable.
>>> 
>>> regards,
>>> Peter
>> 


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

From owner-radiusext@ops.ietf.org  Mon Apr 26 13:51:46 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 0FF1228C16A for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 13:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.455
X-Spam-Level: *
X-Spam-Status: No, score=1.455 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TkEpk5Mv3hGH for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 13:51:45 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 96CD13A6BBA for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 26 Apr 2010 13:51:44 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6VCb-0009sO-0l for radiusext-data0@psg.com; Mon, 26 Apr 2010 20:46:49 +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 1O6VCX-0009oJ-Cf for radiusext@ops.ietf.org; Mon, 26 Apr 2010 20:46:45 +0000
Message-ID: <4BD5FBB3.7070104@deployingradius.com>
Date: Mon, 26 Apr 2010 22:46:43 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: 'Stefan Winter' <mail@stefan-winter.de>, radiusext@ops.ietf.org
Subject: Re: RADEXT WG Last Call on "TLS Encryption for RADIUS" (Experimental)
References: <BLU137-W194A6A55C396F3F124BE81932A0@phx.gbl> <4BCD93B9.6030807@stefan-winter.de> <BLU137-DS346EDD650AB6D0393D2AB93050@phx.gbl>
In-Reply-To: <BLU137-DS346EDD650AB6D0393D2AB93050@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 starting work on a PROTO writeup for this document, on the assumption
> that "lack of response implies consent".  If any issues become apparent 
> in the course of that review, I'll post them to the list. 
> 
> While that's in progress,  WG participants are encouraged to:
> 
> a. Read the document, and post any thoughts to the list (even if that is
> only
> "the document appears ready"); 
> b. Continue to make progress on closing issues within dependency documents 
> (e.g. RADIUS over TCP, Status-Server); 
> c. Post updates on implementation progress; 

  My comments are editorial only.

>...
>  There are multiple known attacks on the MD5 algorithm
>...

  Adding reference(s) would be good.  These can be lifted from RFC 3579,
among others.

>...
>      These middleboxes may learn privacy-
>   relevant data while forwarding requests.
>...

  RADIUS over TLS doesn't solve this problem.  It's still "hop by hop",
and doesn't create "end to end" security.  The use of proxies is still
useful in many environments, and those proxies still have access to all
of the privacy-relevant data.

>...
>   1.  establish TCP connections as per ...
>
>   2.  negotiate TLS sessions according to [RFC5246] or its predecessor
>       TLS 1.1.
>...

  It would be good to note that there is no RADIUS equivalent of
"starttls".  A client and server is marked either as "supporting TLS",
or "not supporting TLS".  So the client/server just "starts TLS" if TLS
is supported.

  i.e. the above text could be understood as "negotiate TLS version and
features", and not "negotiate whether or not to use TLS".

  It may be sufficient to note that step (1) MUST be immediately
followed by step (2), and "bare TCP" on port 2083 MUST NOT be used.


>...
>   In RADIUS/UDP, clients are uniquely identified by their IP address.
>   This does not permit to determine when
>...

  English: This *what* ..

  And elsewhere in the document.  The word "this" should usually be
followed by a specifier, e.g. noun.

  and: Does not permit *who* to determine...?


>...
>3.2.  Ciphersuites and Compression Negotiation Considerations
>
>   Not all TLS ciphersuites in [RFC5246] are supported by available TLS
>   tool kits, and licenses may be required in some cases.  The existing
>   implementations of RADIUS/TLS use OpenSSL as cryptographic backend,
>   which supports all of the ciphersuites listed in the rules in the
>   normative section.
>..

  The implementation text could be put into an "implementation notes"
section.  But it's not serious.

>...
>   (1) After the TLS session is established, RADIUS packet payloads are
>   exchanged over the encrypted TLS tunnel.  In RADIUS/UDP, the packet
>   size can be determined by evaluating the size of the datagram that
>   arrived.  Due to the stream nature of TCP and TLS, this does not >hold
>   true for RADIUS/TLS packet exchange.  Instead, packet boundaries of
>   RADIUS packets that arrive in the stream are calculated by >evaluating
>   the packet's Length field.  Special care needs to be taken on the
>   packet sender side that the value of the Length field is indeed
>   correct before sending it over the TLS tunnel, because incorrect
>   packet lengths can no longer be detected by a differing datagram
>   boundary.
>...

  Adding a reference to RADIUS over TCP, Section 2.6.4 may be good.  It
outlines these issues in more detail.

>...
>   If a given IP device is able to receive RADIUS payloads on multiple
>   transports, this may or may not be the same instance of software,
>and
>   it may or may not serve the same purposes.  It is not safe to assume
>   that both ports are interchangeable.  In particular, it can not be
>   assumed that state is maintained for the packet payloads between the
>   transports.  Two such instances MUST be considered separate RADIUS
>   server entities.
>...

  Ideally, this text should be similar between this doc, the TCP doc,
and the DTLS doc.  I'll take a look at regularizing some of it.

>...
>   If peer communication between two devices is configured for both
>   RADIUS/TLS and RADIUS/UDP, a failover from TLS security to classic
>   RADIUS security opens the way for a down-bidding attack if an
>   adversary can maliciously close the TCP connection, or prevent it
>   from being established.  In this case, security of the packet
> payload
>   is reduced from the selected TLS cipher suite packet encryption to
>   the classic MD5 per-attribute encryption.
>...

  It may be worth discussing how to address that issue.  i.e. both
transports SHOULD be configured only temporarily, as part of a migration
strategy.  Once a secure transport is available, the RADIUS/UDP method
SHOULD be deprecated.  This issue is easier for the TCP document, where
no security means bidding-down isn't an issue.  It's also the subject of
much discussion in the DTLS draft, which re-uses the same server port &&
transport, so bidding-down needs to be handled very carefully.


Nits: the document uses the terms RADIUS/UDP, RADIUS/TCP, and
RADIUS/TLS.  These are not consistent with the TCP or DTLS documents.
It would be good to make all of these consistent across the documents.

  Does the WG have a preference for *which* terminology to use?

  Alan DeKok.

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

From owner-radiusext@ops.ietf.org  Mon Apr 26 23:02:43 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 E82473A63C9 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 23:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.447
X-Spam-Level: *
X-Spam-Status: No, score=1.447 tagged_above=-999 required=5 tests=[AWL=-0.659, 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 fTlrnp+BFAqv for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 26 Apr 2010 23:02:42 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1AE1C3A67E7 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 26 Apr 2010 23:02:41 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6do3-0007Kq-OF for radiusext-data0@psg.com; Tue, 27 Apr 2010 05:58:03 +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 1O6dnz-0007ID-F7 for radiusext@ops.ietf.org; Tue, 27 Apr 2010 05:57:59 +0000
Received: from BLU137-W32 ([65.55.116.7]) by blu0-omc1-s33.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 26 Apr 2010 22:57:59 -0700
Message-ID: <BLU137-W322E5875A303DFF9F9694593030@phx.gbl>
Content-Type: multipart/alternative; boundary="_be14ca7d-4a49-409b-8db1-1b519be1d0b9_"
X-Originating-IP: [64.134.225.224]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
CC: <mail@stefan-winter.de>
Subject: Review of "TLS Encryption for RADIUS" (Experimental)  (part I, Technical)
Date: Mon, 26 Apr 2010 22:57:58 -0700
Importance: Normal
In-Reply-To: <4BD5FBB3.7070104@deployingradius.com>
References: <BLU137-W194A6A55C396F3F124BE81932A0@phx.gbl> <4BCD93B9.6030807@stefan-winter.de> <BLU137-DS346EDD650AB6D0393D2AB93050@phx.gbl>,<4BD5FBB3.7070104@deployingradius.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Apr 2010 05:57:59.0025 (UTC) FILETIME=[96D81E10:01CAE5CE]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_be14ca7d-4a49-409b-8db1-1b519be1d0b9_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


   2.  negotiate TLS sessions according to [RFC5246] or its predecessor
       TLS 1.1.  The following restrictions apply:

       *  The authentication MUST be mutual=2C i.e. both the RADIUS/TLS
          server and the RADIUS/TLS client authenticate each other.

       *  The client MUST NOT negotiate cipher suites which only provide
          integrity protection.

       *  The TLS session MAY use mutual PSKs for connection setup.

       *  Negotiation of compression for the TLS session is OPTIONAL.

       *  RADIUS/TLS implementations MUST support the mandatory to
          implement cipher suites specified in TLS (i.e.
          TLS_RSA_WITH_3DES_EDE_CBC_SHA).  For purposes of compatibility
          with some current deployments implementations SHOULD support
          TLS_RSA_WITH_RC4_128_SHA and TLS_RSA_WITH_AES_128_CBC_SHA as
          well (see Section 3.2 (1) ).

[BA] Several issues with this:

a.  There is no statement about mandatory to implement TLS version (e.g. MU=
ST
support TLS 1.0 and later). =20

b. There is no statement about mandatory to implement authentication mechan=
ism
(e.g. mutual TLS with certificates). =20

Recommend re-writing as follows:

"  2.  negotiate TLS sessions.  The following restrictions apply:

       *  Support for TLS v1.1 [RFC4346] or later (e.g. TLS 1.2 [RFC5246]) =
is REQUIRED.=20

       *  Support for compression is OPTIONAL.=20

       *  Support for certificate-based mutual authentication is REQUIRED.=
=20

       *  Support for TLS-PSK mutual authentication [RFC4279] is OPTIONAL. =
=20

       *  Negotiation of mutual authentication is REQUIRED.=20

       *  Negotiation of a ciphersuite providing for confidentiality as wel=
l
          as integrity protection is REQUIRED. =20

       *  RADIUS/TLS nodes MUST NOT negotiate ciphersuites with NULL encryp=
tion (e.g. [RFC4785]). =20

       *  Negotiation of compression is OPTIONAL.

       *  RADIUS/TLS implementations MUST at a minimum support negotiation
          of the TLS_RSA_WITH_3DES_EDED_CBC_SHA ciphersuite=2C and SHOULD
          support TLS_RSA_WITH_RC4_128_SHA and TLS_RSA_WITH_AES_128_CBC_SHA=
 as
          well (see Section 3.2 (1) ).

       *  In addition=2C RADIUS/TLS implementations MUST support negotiatio=
n of
          the mandatory-to-implement ciphersuites required by the versions =
of TLS
          that they support." =20



       *  Certificate validation MUST include the verification rules as
          per [RFC5280]=2C using information from trusted sources only
          (e.g. locally configured names).  If service names as per
          [RFC4985] are present in the certificate and dynamic discovery
          utilizing SRVs in DNS is used (see
          [I-D.winter-dynamic-discovery]) and the TLS implementation
          supports evaluation of the extensions in [RFC4985]=2C the SRV
          entry MUST be validated.  In cases where no DNS SRV resolution
          took place to arrive at the TLS peer=2C subjectAltName:SRV
          entries can be ignored.


[BA]  I'm not clear what "using information from trusted sources only"
means=2C exactly.=20

Given the MUST here=2C the reference to dynamic discovery is probably
normative.  My suggestion is to move this material to the dynamic discovery
draft so as to remove the normative dependency. =20

Among other things=2C moving this to the dynamic discovery document will
provide some additional time to think through the security issues. =20

Use of the extensions in [RFC4985] does not necessarily address the
problem of forgery of DNS SRV RRs unless some kind of name constraint is al=
so
applied.  For example=2C an attacker could forge an SRV RR that indicates t=
hat the
RADIUS/TLS server for example.com is hosted with the evilhacker.com domain=
=2C and
the fradulent RADIUS/TLS server could provide a valid certificate with a
service extenion indicating its acting as the RADIUS/TLS server for example=
.com.=20
The problem is that the certificate chain will not include a trust anchor w=
ithin
the example.com domain. =20

2.3. Connecting Client Identity

   In RADIUS/UDP=2C 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=2C it also does not permit to determine
   whether there is more than one entity connecting from the same IP
   address.

[BA] The NAS is identified by the NAS-Identifier/NAS-IP-Address/NAS-IPv6-Ad=
dress
attributes=2C no?  Since RADIUS identifies entities by IP address=2C by
definition all packets originating from a given IP address are assumed
to come from the same entity.  Suggest rewriting as follows:

 " In RADIUS/UDP=2C clients are uniquely identified by their IP address.
   Since the shared secret is associated with the origin IP address=2C=20
   if more than one RADIUS client is associated with the same IP
   address=2C then those clients also must utilize the same shared secret=
=2C
   a practice which is inherently insecure as noted in [RFC5247]."


   RADIUS/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=2C it permits 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/TLS should expose as many details of the
   TLS connection which belongs to an incoming RADIUS packet as possible
   to the application layer to allow the administrator to define the
   identification criteria which are applicable to his desired
   operational model.  In X.509 certificate operation=2C 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=2C at least the following parameters of the TLS
   connection should be exposed:

   o  Originating IP address

   o  TLS Identifier

[BA] It seems to me that the above text is somewhat too vague in that it do=
esn't
precisely define what parameters should be used to differentiate RADIUS cli=
ents
and servers from each other.=20

2.4. RADIUS Datagrams

   Authentication=2C Accounting and Authorization packets are sent
   according to the following rules:

   RADIUS/TLS clients handle the following packet types from [RFC2865]=2C
   [RFC2866]=2C [RFC5176] on the connection they initiated (see
   Section 3.3 (3) and (4) ):

   o  send Access-Request

   o  send Accounting-Request

   o  send Status-Server

   o  send Disconnect-ACK

   o  send Disconnect-NAK

   o  send CoA-ACK

   o  send CoA-NAK

   o  receive Access-Challenge

   o  receive Access-Accept

   o  receive Access-Reject

   o  receive Accounting-Response

   o  receive Disconnect-Request

   o  receive CoA-Request

   RADIUS/TLS servers handle the following packet types from [RFC2865]=2C
   [RFC2866]=2C [RFC5176] on the connections they serve to clients:

   o  receive Access-Request

   o  receive Accounting-Request

   o  receive Status-Server

   o  receive Disconnect-ACK

   o  receive Disconnect-NAK

   o  receive CoA-ACK

   o  receive CoA-NAK

   o  send Access-Challenge

   o  send Access-Accept

   o  send Access-Reject

   o  send Accounting-Response

   o  send Disconnect-Request

   o  send CoA-Request

[BA] This assumes that the RADIUS server is also a Dynamic Authorization Cl=
ient.  This is not=20
necessarily the case.   CoA-Request and Disconnect-Request packets can also=
 be sent by a=20
DAC that originates its own TLS connection=2C no?=20

My suggestion is that you separate the DAC/DAS roles from the RADIUS client=
/server roles in this
section.  I'd also note that the RADIUS over TCP document does not recommen=
d that Dynamic
Authorization traffic be sent over TLS. =20
 		 	   		  =

--_be14ca7d-4a49-409b-8db1-1b519be1d0b9_
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'>
&nbsp=3B&nbsp=3B 2.&nbsp=3B negotiate TLS sessions according to [RFC5246] o=
r its predecessor<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B TLS 1=
.1.&nbsp=3B The following restrictions apply:<br><br>&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B The authentication MUST be mutual=2C =
i.e. both the RADIUS/TLS<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B server and the RADIUS/TLS client authenticate e=
ach other.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=
=3B The client MUST NOT negotiate cipher suites which only provide<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B integri=
ty protection.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nb=
sp=3B The TLS session MAY use mutual PSKs for connection setup.<br><br>&nbs=
p=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Negotiation of compr=
ession for the TLS session is OPTIONAL.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbs=
p=3B&nbsp=3B&nbsp=3B *&nbsp=3B RADIUS/TLS implementations MUST support the =
mandatory to<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B implement cipher suites specified in TLS (i.e.<br>&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B TLS_RSA_WITH_=
3DES_EDE_CBC_SHA).&nbsp=3B For purposes of compatibility<br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B with some curre=
nt deployments implementations SHOULD support<br>&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B TLS_RSA_WITH_RC4_128_SHA and=
 TLS_RSA_WITH_AES_128_CBC_SHA as<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B well (see Section 3.2 (1) ).<br><br>[BA=
] Several issues with this:<br><br>a.&nbsp=3B There is no statement about m=
andatory to implement TLS version (e.g. MUST<br>support TLS 1.0 and later).=
 &nbsp=3B<br><br>b. There is no statement about mandatory to implement auth=
entication mechanism<br>(e.g. mutual TLS with certificates). &nbsp=3B<br><b=
r>Recommend re-writing as follows:<br><br>"&nbsp=3B 2.&nbsp=3B negotiate TL=
S sessions.&nbsp=3B The following restrictions apply:<br><br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Support for TLS v1.1 [RFC4346=
] or later (e.g. TLS 1.2 [RFC5246]) is REQUIRED. <br><br>&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Support for compression is OPTIONA=
L. <br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Suppo=
rt for certificate-based mutual authentication is REQUIRED. <br><br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Support for TLS-PSK m=
utual authentication [RFC4279] is OPTIONAL. &nbsp=3B<br><br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Negotiation of mutual authent=
ication is REQUIRED. <br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B *&nbsp=3B Negotiation of a ciphersuite providing for confidentiality as=
 well<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B as integrity protection is REQUIRED. &nbsp=3B<br><br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B RADIUS/TLS nodes MUST NOT neg=
otiate ciphersuites with NULL encryption (e.g. [RFC4785]). &nbsp=3B<br><br>=
&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Negotiation of c=
ompression is OPTIONAL.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbs=
p=3B *&nbsp=3B RADIUS/TLS implementations MUST at a minimum support negotia=
tion<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B of the TLS_RSA_WITH_3DES_EDED_CBC_SHA ciphersuite=2C and SHOULD<br>&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B supp=
ort TLS_RSA_WITH_RC4_128_SHA and TLS_RSA_WITH_AES_128_CBC_SHA as<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B well (s=
ee Section 3.2 (1) ).<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B *&nbsp=3B In addition=2C RADIUS/TLS implementations MUST support negoti=
ation of<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B the mandatory-to-implement ciphersuites required by the version=
s of TLS<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B that they support." &nbsp=3B<br><br><br><br>&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Certificate validation MUST include=
 the verification rules as<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B per [RFC5280]=2C using information from trusted=
 sources only<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B (e.g. locally configured names).&nbsp=3B If service names as=
 per<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B [RFC4985] are present in the certificate and dynamic discovery<br>&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B utili=
zing SRVs in DNS is used (see<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B [I-D.winter-dynamic-discovery]) and the TLS =
implementation<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&=
nbsp=3B&nbsp=3B supports evaluation of the extensions in [RFC4985]=2C the S=
RV<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B entry MUST be validated.&nbsp=3B In cases where no DNS SRV resolution<b=
r>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B =
took place to arrive at the TLS peer=2C subjectAltName:SRV<br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B entries can be =
ignored.<br><br><br>[BA]&nbsp=3B I'm not clear what "using information from=
 trusted sources only"<br>means=2C exactly. <br><br>Given the MUST here=2C =
the reference to dynamic discovery is probably<br>normative.&nbsp=3B My sug=
gestion is to move this material to the dynamic discovery<br>draft so as to=
 remove the normative dependency. &nbsp=3B<br><br>Among other things=2C mov=
ing this to the dynamic discovery document will<br>provide some additional =
time to think through the security issues. &nbsp=3B<br><br>Use of the exten=
sions in [RFC4985] does not necessarily address the<br>problem of forgery o=
f DNS SRV RRs unless some kind of name constraint is also<br>applied.&nbsp=
=3B For example=2C an attacker could forge an SRV RR that indicates that th=
e<br>RADIUS/TLS server for example.com is hosted with the evilhacker.com do=
main=2C and<br>the fradulent RADIUS/TLS server could provide a valid certif=
icate with a<br>service extenion indicating its acting as the RADIUS/TLS se=
rver for example.com. <br>The problem is that the certificate chain will no=
t include a trust anchor within<br>the example.com domain. &nbsp=3B<br><br>=
2.3. Connecting Client Identity<br><br>&nbsp=3B&nbsp=3B In RADIUS/UDP=2C cl=
ients are uniquely identified by their IP address.<br>&nbsp=3B&nbsp=3B This=
 does not permit to determine whether the connecting entity is a<br>&nbsp=
=3B&nbsp=3B NAS or a different server which proxies a request.&nbsp=3B When=
 NAT is used<br>&nbsp=3B&nbsp=3B on the path to the server=2C it also does =
not permit to determine<br>&nbsp=3B&nbsp=3B whether there is more than one =
entity connecting from the same IP<br>&nbsp=3B&nbsp=3B address.<br><br>[BA]=
 The NAS is identified by the NAS-Identifier/NAS-IP-Address/NAS-IPv6-Addres=
s<br>attributes=2C no?&nbsp=3B Since RADIUS identifies entities by IP addre=
ss=2C by<br>definition all packets originating from a given IP address are =
assumed<br>to come from the same entity.&nbsp=3B Suggest rewriting as follo=
ws:<br><br>&nbsp=3B" In RADIUS/UDP=2C clients are uniquely identified by th=
eir IP address.<br>&nbsp=3B&nbsp=3B Since the shared secret is associated w=
ith the origin IP address=2C <br>&nbsp=3B&nbsp=3B if more than one RADIUS c=
lient is associated with the same IP<br>&nbsp=3B&nbsp=3B address=2C then th=
ose clients also must utilize the same shared secret=2C<br>&nbsp=3B&nbsp=3B=
 a practice which is inherently insecure as noted in [RFC5247]."<br><br><br=
>&nbsp=3B&nbsp=3B RADIUS/TLS makes it possible to preserve this traditional=
 RADIUS<br>&nbsp=3B&nbsp=3B semantics by identifying a connecting client by=
 the IP address which<br>&nbsp=3B&nbsp=3B initiated the TLS connection.&nbs=
p=3B In addition=2C it permits a much more<br>&nbsp=3B&nbsp=3B fine-grained=
 identification.&nbsp=3B The parameters of the TLS connection<br>&nbsp=3B&n=
bsp=3B can be attributed to the RADIUS packets inside the TLS connection.<b=
r>&nbsp=3B&nbsp=3B An implementation of RADIUS/TLS should expose as many de=
tails of the<br>&nbsp=3B&nbsp=3B TLS connection which belongs to an incomin=
g RADIUS packet as possible<br>&nbsp=3B&nbsp=3B to the application layer to=
 allow the administrator to define the<br>&nbsp=3B&nbsp=3B identification c=
riteria which are applicable to his desired<br>&nbsp=3B&nbsp=3B operational=
 model.&nbsp=3B In X.509 certificate operation=2C at least the<br>&nbsp=3B&=
nbsp=3B following parameters of the TLS connection should be exposed:<br><b=
r>&nbsp=3B&nbsp=3B o&nbsp=3B Originating IP address<br><br>&nbsp=3B&nbsp=3B=
 o&nbsp=3B Certificate Fingerprint<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B Issuer=
<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B Subject<br><br>&nbsp=3B&nbsp=3B o&nbsp=
=3B all X509v3 Extended Key Usage<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B all X50=
9v3 Subject Alternative Name<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B all X509v3 C=
ertificate Policies<br><br>&nbsp=3B&nbsp=3B In TLS-PSK operation=2C at leas=
t the following parameters of the TLS<br>&nbsp=3B&nbsp=3B connection should=
 be exposed:<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B Originating IP address<br><b=
r>&nbsp=3B&nbsp=3B o&nbsp=3B TLS Identifier<br><br>[BA] It seems to me that=
 the above text is somewhat too vague in that it doesn't<br>precisely defin=
e what parameters should be used to differentiate RADIUS clients<br>and ser=
vers from each other. <br><br>2.4. RADIUS Datagrams<br><br>&nbsp=3B&nbsp=3B=
 Authentication=2C Accounting and Authorization packets are sent<br>&nbsp=
=3B&nbsp=3B according to the following rules:<br><br>&nbsp=3B&nbsp=3B RADIU=
S/TLS clients handle the following packet types from [RFC2865]=2C<br>&nbsp=
=3B&nbsp=3B [RFC2866]=2C [RFC5176] on the connection they initiated (see<br=
>&nbsp=3B&nbsp=3B Section 3.3 (3) and (4) ):<br><br>&nbsp=3B&nbsp=3B o&nbsp=
=3B send Access-Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send Accounting-R=
equest<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send Status-Server<br><br>&nbsp=3B=
&nbsp=3B o&nbsp=3B send Disconnect-ACK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B se=
nd Disconnect-NAK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send CoA-ACK<br><br>&nb=
sp=3B&nbsp=3B o&nbsp=3B send CoA-NAK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B rece=
ive Access-Challenge<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Access-Accep=
t<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Access-Reject<br><br>&nbsp=3B&n=
bsp=3B o&nbsp=3B receive Accounting-Response<br><br>&nbsp=3B&nbsp=3B o&nbsp=
=3B receive Disconnect-Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Co=
A-Request<br><br>&nbsp=3B&nbsp=3B RADIUS/TLS servers handle the following p=
acket types from [RFC2865]=2C<br>&nbsp=3B&nbsp=3B [RFC2866]=2C [RFC5176] on=
 the connections they serve to clients:<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B r=
eceive Access-Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Accounting-=
Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Status-Server<br><br>&nbs=
p=3B&nbsp=3B o&nbsp=3B receive Disconnect-ACK<br><br>&nbsp=3B&nbsp=3B o&nbs=
p=3B receive Disconnect-NAK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive CoA-A=
CK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive CoA-NAK<br><br>&nbsp=3B&nbsp=
=3B o&nbsp=3B send Access-Challenge<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send =
Access-Accept<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send Access-Reject<br><br>&=
nbsp=3B&nbsp=3B o&nbsp=3B send Accounting-Response<br><br>&nbsp=3B&nbsp=3B =
o&nbsp=3B send Disconnect-Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send Co=
A-Request<br><br>[BA] This assumes that the RADIUS server is also a Dynamic=
 Authorization Client.&nbsp=3B This is not <br>necessarily the case.&nbsp=
=3B&nbsp=3B CoA-Request and Disconnect-Request packets can also be sent by =
a <br>DAC that originates its own TLS connection=2C no? <br><br>My suggesti=
on is that you separate the DAC/DAS roles from the RADIUS client/server rol=
es in this<br>section.&nbsp=3B I'd also note that the RADIUS over TCP docum=
ent does not recommend that Dynamic<br>Authorization traffic be sent over T=
LS.&nbsp=3B <br> 		 	   		  </body>
</html>=

--_be14ca7d-4a49-409b-8db1-1b519be1d0b9_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 27 01:54: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 624FE3A6C5D for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 01:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.21
X-Spam-Level: 
X-Spam-Status: No, score=0.21 tagged_above=-999 required=5 tests=[AWL=-1.895, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGfRuF7FoqBd for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 01:54:02 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id D30413A67E3 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 27 Apr 2010 01:53:12 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6gUJ-000JtL-Gy for radiusext-data0@psg.com; Tue, 27 Apr 2010 08:49:51 +0000
Received: from [198.152.13.100] (helo=co300216-co-outbound.net.avaya.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <dromasca@avaya.com>) id 1O6gU8-000JpO-H9 for radiusext@ops.ietf.org; Tue, 27 Apr 2010 08:49:40 +0000
X-IronPort-AV: E=Sophos;i="4.52,279,1270440000";  d="scan'208";a="215336392"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 27 Apr 2010 04:49:33 -0400
X-IronPort-AV: E=Sophos;i="4.52,279,1270440000";  d="scan'208";a="455262661"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 27 Apr 2010 04:49:33 -0400
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: AD review of draft-ietf-radext-tcp-transport-05
Date: Tue, 27 Apr 2010 10:49:31 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402145193@307622ANEX5.global.avaya.com>
In-Reply-To: <4BD5C58D.6040303@deployingradius.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AD review of draft-ietf-radext-tcp-transport-05
Thread-Index: AcrlYVJxWkIe1wouROOKTEf1H7LjLwAhOA+g
References: <EDC652A26FB23C4EB6384A4584434A0401FFEFAC@307622ANEX5.global.avaya.com> <4BD5C58D.6040303@deployingradius.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Alan DeKok" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hi Alan,

Thank you for the answers. The proposed changes answer my concerns and I
suggest that you go ahead with issuing a revised I-D.=20

The only terms I am still a little bit uncertain about are 'common
Internet MTU' and 'common Ethernet MTU' but I understand what you mean
and I cannot find a better term. Let us use them, and  maybe other will
find something better as a term in future reviews.=20

Regards,

Dan
 =20

> -----Original Message-----
> From: Alan DeKok [mailto:aland@deployingradius.com]=20
> Sent: Monday, April 26, 2010 7:56 PM
> To: Romascanu, Dan (Dan)
> Cc: radiusext@ops.ietf.org
> Subject: Re: AD review of draft-ietf-radext-tcp-transport-05
>=20
> Romascanu, Dan (Dan) wrote:
> > The issues are divided into Technical (T) and Editorial (E).=20
> >=20
> > T1. The document is marked as EXPERIMENTAL. It would be=20
> useful if it=20
> > mentions in one of the introductory sections what are the goals and=20
> > limitations (if any) of the experimental deployment and=20
> what would be=20
> > the success criteria of the experiment that would allow for=20
> taking the=20
> > document to the standards track later.
>=20
>   Suggested text for Section 1 (Introduction).  Move the last=20
> paragraph from Section 1.2 to higher up in the document, and=20
> add some text:
>=20
> ...
> Since "bare" TCP does not provide for confidentiality or=20
> enable negotiation of credible ciphersuites, its use is not=20
> appropriate for inter-server communications where strong=20
> security is required.  As a result the use of "bare" TCP=20
> transport (i.e., without additional confidentiality and=20
> security) is NOT RECOMMENDED, as there has been little or no=20
> operational experience with it.
>=20
> "Bare" TCP transport MAY, however, be used when another=20
> method such as IPSec [RFC4301] is used to provide additional=20
> confidentiality and security.  Should experience show that=20
> such deployments are useful, this specification could be=20
> moved to standards track.
> ...
>=20
> > T2. Section 2.2:=20
> >=20
> >>  Since these ports are unused by existing RADIUS=20
> implementations, the
> >    assigned values SHOULD be used as the default ports for=20
> RADIUS over
> >    TCP.
> >=20
> > Why is this a SHOULD and not a MUST?=20
>=20
>   No reason...  I'll change it.
>=20
> > T3. Section 2.3 needs a complete re-writing:=20
> ...
> > The correct solution is for the MIB documents to be updated in the=20
> > future with new MIB objects of appropriate syntax. For the=20
> time being=20
> > the only thing that this section should say is that the MIB=20
> modules do=20
> > not support RADIUS over TCP and that they will need to be=20
> updated in=20
> > the future.
>=20
>   Suggest replacing the text in 2.3 with:
>=20
> The MIB Module definitions in [RFC4668], [RFC4669],=20
> [RFC4670], [RFC4671], [RFC4672], and [RFC4673] are intended=20
> to be used for RADIUS over UDP.  As such, they do not support=20
> RADIUS over TCP, and will need to be updated in the future. =20
> Implementations of RADIUS over TCP SHOULD NOT re-use these=20
> MIB Modules to perform statistics counting for RADIUS over=20
> TCP connections.
>=20
> > T4. The following section in 2.6.1 is confusing:=20
> >=20
> >>  Much of the discussion in this section can be summarized by the
> >    following requirement.  RADIUS requests MAY be re-transmitted
> >    verbatim only if the following 5-tuple (Client IP address, Client
> >    port, Transport Protocol, Server IP address, Server=20
> port) remains the
> >    same.=20
>=20
>   I think it's best to simply delete that paragraph.
>=20
> > T5. The last paragraph in 2.6.1:=20
> >=20
> >>   The above requirement is necessary, but not sufficient=20
> in all cases.
> >    Other specifications give additional situations where=20
> the packet is
> >    to be considered as a new request.  Those=20
> recommendations MUST also
> >    be followed.
> >=20
> > Having a MUST requirement over undefined 'other=20
> specification' is not=20
> > implementable. I would suggest to either clarify what are=20
> these 'other=20
> > specifications' or take this out.
>=20
>   OK.  I'll delete it.
>=20
> > E1. Please expand TLS at first occurrence.=20
>=20
>   Done.
>=20
> > E2. The Introduction section speaks about 'the default Internet MTU=20
> > (576). Strictly speaking this value is not standardized in=20
> any place,
>=20
>   That should be the "common Internet MTU".  The text could say:
>=20
> These packets are larger than the common Internet MTU (576),=20
> resulting in fragmentation of the packets at the IP layer=20
> when they are proxied over the Internet.
>=20
> > and later in section 1.1 reference is made to RADIUS packets being=20
> > restricted to 1500 octets in size. Looks like an unnecessary=20
> > inconsistency.
>=20
>   That is for a different use-case.  I can update that text to say:
>=20
> For example, where EAP-TLS authentication [RFC5216] is=20
> attempted and both the EAP peer and server utilize=20
> certificate chains of 8KB, as many as 15 round-trips can be=20
> required if RADIUS packets are restricted to the common=20
> Ethernet MTU (1500 octets) for EAP over LAN (EAPoL) use-cases.
>=20
> > E3. Section 1.2 - the syntax in the RADIUS server definition is=20
> > inconsistent with the syntax of the rest of the definitions
>=20
>   OK.  That could say:
>=20
> A device that provides one or more of authentication,=20
> authorization, and/or accounting (AAA) services to a NAS.
>=20
>=20
> > E4. Section 2.6.7:=20
> >=20
> >>  We RECOMMEND that implementors of this specification
> >    familiarize themselves with TCP application programming=20
> concepts.  We
> >    RECOMMEND also that existing TCP applications be=20
> examined with an eye
> >    to robustness, performance, scalability, etc.
> >=20
> > The use of capitalized (a la 2119) keywords in a=20
> personalized phrase=20
> > does not make much sense. RECOMMEND is not a keyword actually. I=20
> > suggest rephrasing.
>=20
>   Changed to: "It is RECOMMENDED that..."
>=20
>   If this looks OK, I'll issue an updated draft tomorrow.
>=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  Tue Apr 27 02:56: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 A4EEA3A69DE for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 02:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.455
X-Spam-Level: *
X-Spam-Status: No, score=1.455 tagged_above=-999 required=5 tests=[AWL=-0.464, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0POmSi-wQfuT for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 02:56:12 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 915903A6A5D for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 27 Apr 2010 02:55:59 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6hSb-0008Vd-IJ for radiusext-data0@psg.com; Tue, 27 Apr 2010 09:52: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 1O6hSY-0008Tb-Hp for radiusext@ops.ietf.org; Tue, 27 Apr 2010 09:52:06 +0000
Message-ID: <4BD6B3C5.6070308@deployingradius.com>
Date: Tue, 27 Apr 2010 11:52:05 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Bernard's notes
References: <BLU137-W20CFFD1E4C3104581A412393050@phx.gbl>
In-Reply-To: <BLU137-W20CFFD1E4C3104581A412393050@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:
> Just a note to the WG to summarize where I think we are on various work
> items.  The hope is that this note will disclose any disconnects which
> could lead to things falling through the cracks.
> 
> Issue List (recently updated): http://www.drizzle.com/~aboba/RADEXT/
> 
> 1. Completed IESG Review: Revision Needed
> 
> My notes show two documents in this category:  Design Guidelines and
> Status Server.  In both cases, it appears to me that the editor (Alan
> DeKok) is holding the token.

  I've made suggestions on the list for updates to address the open
issues.

> Status Server
> 
> This document currently has IESG DISCUSS comments open (see Issue #333),
> in addition to IETF last call comments (Issue # 330). 
> 
> Next steps:  The editor need to address the open issues, preferably by
> posting a document revision. 

  Posted.

> 2. AD Review:  Revision Needed
> 
> My notes show one document in this category:  RADIUS over TCP, with the
> editor (Alan DeKok) holding the token..
> 
> There are two open issues relating to the Dan's AD review:  Issues 331
> (technical) and 332 (editorial). 
> 
> Next steps:  The editor needs to address the open issues, preferably by
> posting a document revision.

  Posted.

  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 Apr 27 03:03: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 05E5B3A6896 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 03:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.079
X-Spam-Level: 
X-Spam-Status: No, score=-102.079 tagged_above=-999 required=5 tests=[AWL=0.522, 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 aTd0u0qobyVM for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 03:03:34 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 32ABB3A6857 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 27 Apr 2010 03:03:23 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6haB-000AXP-GO for radiusext-data0@psg.com; Tue, 27 Apr 2010 09:59:59 +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 1O6ha3-000ATs-84 for radiusext@ops.ietf.org; Tue, 27 Apr 2010 09:59:51 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id 0AA453A6A3B; Tue, 27 Apr 2010 03:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-status-server-07.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100427100002.0AA453A6A3B@core3.amsl.com>
Date: Tue, 27 Apr 2010 03:00:02 -0700 (PDT)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : 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-07.txt
	Pages           : 25
	Date            : 2010-04-27

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

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

--NextPart--

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

From owner-radiusext@ops.ietf.org  Tue Apr 27 03:05: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 406F13A683B for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 03:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.087
X-Spam-Level: 
X-Spam-Status: No, score=-102.087 tagged_above=-999 required=5 tests=[AWL=0.513, 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 C4uHoBtyURAx for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 03:05:13 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 50A8F3A67F8 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 27 Apr 2010 03:05:13 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6haC-000AXb-6L for radiusext-data0@psg.com; Tue, 27 Apr 2010 10:00:00 +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 1O6ha4-000AUY-72 for radiusext@ops.ietf.org; Tue, 27 Apr 2010 09:59:52 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id 169A23A6A5D; Tue, 27 Apr 2010 03:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-tcp-transport-06.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100427100002.169A23A6A5D@core3.amsl.com>
Date: Tue, 27 Apr 2010 03:00:02 -0700 (PDT)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : RADIUS Over TCP
	Author(s)       : A. DeKok
	Filename        : draft-ietf-radext-tcp-transport-06.txt
	Pages           : 18
	Date            : 2010-04-27

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 Transport Layer Security [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-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-tcp-transport-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--NextPart--

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

From owner-radiusext@ops.ietf.org  Tue Apr 27 07:15: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 870933A6B8E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 07:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wIzxO0cJN3oI for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 27 Apr 2010 07:15:55 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id DADC73A6A0D for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 27 Apr 2010 07:12:49 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O6lSa-000EXe-BH for radiusext-data0@psg.com; Tue, 27 Apr 2010 14:08:24 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <wwwrun@core3.amsl.com>) id 1O6lSX-000EWG-Rx for radiusext@ops.ietf.org; Tue, 27 Apr 2010 14:08:22 +0000
Received: by core3.amsl.com (Postfix, from userid 30) id 8800028C12E; Tue, 27 Apr 2010 07:08:32 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Reply-to: ietf@ietf.org
CC: <radiusext@ops.ietf.org>
Subject: Last Call: draft-ietf-radext-tcp-transport (RADIUS Over TCP) to Experimental RFC
Message-Id: <20100427140832.8800028C12E@core3.amsl.com>
Date: Tue, 27 Apr 2010 07:08:32 -0700 (PDT)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

The IESG has received a request from the RADIUS EXTensions WG (radext) to 
consider the following document:

- 'RADIUS Over TCP '
   <draft-ietf-radext-tcp-transport-06.txt> as an Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-05-11. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-radext-tcp-transport-06.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18053&rfc_flag=0


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
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 Apr 29 02:24:26 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 271D128C224 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 29 Apr 2010 02:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.475
X-Spam-Level: 
X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.125, 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 U9InSs5g8RBm for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 29 Apr 2010 02:24:25 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0585128C276 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 29 Apr 2010 02:19:38 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1O7Ppc-000O1S-TA for radiusext-data0@psg.com; Thu, 29 Apr 2010 09:14:52 +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 1O7Ppa-000O10-Ek for radiusext@ops.ietf.org; Thu, 29 Apr 2010 09:14:50 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id 4109128C253; Thu, 29 Apr 2010 02:15:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-ipv6-access-01.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100429091502.4109128C253@core3.amsl.com>
Date: Thu, 29 Apr 2010 02:15:02 -0700 (PDT)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : RADIUS attributes for IPv6 Access Networks
	Author(s)       : B. Lourdelet, et al.
	Filename        : draft-ietf-radext-ipv6-access-01.txt
	Pages           : 13
	Date            : 2010-04-29

IPv6 nodes can have configuration information provided to them using
DHCPv6 and/or Router Advertisements.  This document specifies RADIUS
attributes that complement RFC3162 for use with DHCPv6 and/or Router
Advertisements (RAs) and their application in broadband network
access.

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

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

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

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

Content-Type: text/plain
Content-ID:     <2010-04-29020205.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: Thu, 29 Apr 2010 09:15:46 +0000
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-ipv6-access-01.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100429091502.4109128C253@core3.amsl.com>
Date: Thu, 29 Apr 2010 02:15:02 -0700 (PDT)

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : RADIUS attributes for IPv6 Access Networks
	Author(s)       : B. Lourdelet, et al.
	Filename        : draft-ietf-radext-ipv6-access-01.txt
	Pages           : 13
	Date            : 2010-04-29

IPv6 nodes can have configuration information provided to them using
DHCPv6 and/or Router Advertisements.  This document specifies RADIUS
attributes that complement RFC3162 for use with DHCPv6 and/or Router
Advertisements (RAs) and their application in broadband network
access.

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

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

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

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

Content-Type: text/plain
Content-ID:     <2010-04-29020205.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, 27 Apr 2010 14:09:01 +0000
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Reply-to: ietf@ietf.org
CC: <radiusext@ops.ietf.org>
Subject: Last Call: draft-ietf-radext-tcp-transport (RADIUS Over TCP) to Experimental RFC
Message-Id: <20100427140832.8800028C12E@core3.amsl.com>
Date: Tue, 27 Apr 2010 07:08:32 -0700 (PDT)

The IESG has received a request from the RADIUS EXTensions WG (radext) to 
consider the following document:

- 'RADIUS Over TCP '
   <draft-ietf-radext-tcp-transport-06.txt> as an Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-05-11. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-radext-tcp-transport-06.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18053&rfc_flag=0


--
to unsubscribe send a message to radiusext-request@ops.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, 27 Apr 2010 10:00:28 +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-07.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100427100002.0AA453A6A3B@core3.amsl.com>
Date: Tue, 27 Apr 2010 03:00:02 -0700 (PDT)

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : 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-07.txt
	Pages           : 25
	Date            : 2010-04-27

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

Content-Type: text/plain
Content-ID:     <2010-04-27025138.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, 27 Apr 2010 10:00:19 +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-06.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100427100002.169A23A6A5D@core3.amsl.com>
Date: Tue, 27 Apr 2010 03:00:02 -0700 (PDT)

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : RADIUS Over TCP
	Author(s)       : A. DeKok
	Filename        : draft-ietf-radext-tcp-transport-06.txt
	Pages           : 18
	Date            : 2010-04-27

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 Transport Layer Security [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-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-tcp-transport-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2010-04-27025144.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, 27 Apr 2010 09:53:09 +0000
Message-ID: <4BD6B3C5.6070308@deployingradius.com>
Date: Tue, 27 Apr 2010 11:52:05 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Bernard's notes
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> Just a note to the WG to summarize where I think we are on various work
> items.  The hope is that this note will disclose any disconnects which
> could lead to things falling through the cracks.
> 
> Issue List (recently updated): http://www.drizzle.com/~aboba/RADEXT/
> 
> 1. Completed IESG Review: Revision Needed
> 
> My notes show two documents in this category:  Design Guidelines and
> Status Server.  In both cases, it appears to me that the editor (Alan
> DeKok) is holding the token.

  I've made suggestions on the list for updates to address the open
issues.

> Status Server
> 
> This document currently has IESG DISCUSS comments open (see Issue #333),
> in addition to IETF last call comments (Issue # 330). 
> 
> Next steps:  The editor need to address the open issues, preferably by
> posting a document revision. 

  Posted.

> 2. AD Review:  Revision Needed
> 
> My notes show one document in this category:  RADIUS over TCP, with the
> editor (Alan DeKok) holding the token..
> 
> There are two open issues relating to the Dan's AD review:  Issues 331
> (technical) and 332 (editorial). 
> 
> Next steps:  The editor needs to address the open issues, preferably by
> posting a document revision.

  Posted.

  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, 27 Apr 2010 08:50:33 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: AD review of draft-ietf-radext-tcp-transport-05
Date: Tue, 27 Apr 2010 10:49:31 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402145193@307622ANEX5.global.avaya.com>
Thread-Topic: AD review of draft-ietf-radext-tcp-transport-05
Thread-Index: AcrlYVJxWkIe1wouROOKTEf1H7LjLwAhOA+g
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Alan DeKok" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>

Hi Alan,

Thank you for the answers. The proposed changes answer my concerns and I
suggest that you go ahead with issuing a revised I-D.=20

The only terms I am still a little bit uncertain about are 'common
Internet MTU' and 'common Ethernet MTU' but I understand what you mean
and I cannot find a better term. Let us use them, and  maybe other will
find something better as a term in future reviews.=20

Regards,

Dan
 =20

> -----Original Message-----
> From: Alan DeKok [mailto:aland@deployingradius.com]=20
> Sent: Monday, April 26, 2010 7:56 PM
> To: Romascanu, Dan (Dan)
> Cc: radiusext@ops.ietf.org
> Subject: Re: AD review of draft-ietf-radext-tcp-transport-05
>=20
> Romascanu, Dan (Dan) wrote:
> > The issues are divided into Technical (T) and Editorial (E).=20
> >=20
> > T1. The document is marked as EXPERIMENTAL. It would be=20
> useful if it=20
> > mentions in one of the introductory sections what are the goals and=20
> > limitations (if any) of the experimental deployment and=20
> what would be=20
> > the success criteria of the experiment that would allow for=20
> taking the=20
> > document to the standards track later.
>=20
>   Suggested text for Section 1 (Introduction).  Move the last=20
> paragraph from Section 1.2 to higher up in the document, and=20
> add some text:
>=20
> ...
> Since "bare" TCP does not provide for confidentiality or=20
> enable negotiation of credible ciphersuites, its use is not=20
> appropriate for inter-server communications where strong=20
> security is required.  As a result the use of "bare" TCP=20
> transport (i.e., without additional confidentiality and=20
> security) is NOT RECOMMENDED, as there has been little or no=20
> operational experience with it.
>=20
> "Bare" TCP transport MAY, however, be used when another=20
> method such as IPSec [RFC4301] is used to provide additional=20
> confidentiality and security.  Should experience show that=20
> such deployments are useful, this specification could be=20
> moved to standards track.
> ...
>=20
> > T2. Section 2.2:=20
> >=20
> >>  Since these ports are unused by existing RADIUS=20
> implementations, the
> >    assigned values SHOULD be used as the default ports for=20
> RADIUS over
> >    TCP.
> >=20
> > Why is this a SHOULD and not a MUST?=20
>=20
>   No reason...  I'll change it.
>=20
> > T3. Section 2.3 needs a complete re-writing:=20
> ...
> > The correct solution is for the MIB documents to be updated in the=20
> > future with new MIB objects of appropriate syntax. For the=20
> time being=20
> > the only thing that this section should say is that the MIB=20
> modules do=20
> > not support RADIUS over TCP and that they will need to be=20
> updated in=20
> > the future.
>=20
>   Suggest replacing the text in 2.3 with:
>=20
> The MIB Module definitions in [RFC4668], [RFC4669],=20
> [RFC4670], [RFC4671], [RFC4672], and [RFC4673] are intended=20
> to be used for RADIUS over UDP.  As such, they do not support=20
> RADIUS over TCP, and will need to be updated in the future. =20
> Implementations of RADIUS over TCP SHOULD NOT re-use these=20
> MIB Modules to perform statistics counting for RADIUS over=20
> TCP connections.
>=20
> > T4. The following section in 2.6.1 is confusing:=20
> >=20
> >>  Much of the discussion in this section can be summarized by the
> >    following requirement.  RADIUS requests MAY be re-transmitted
> >    verbatim only if the following 5-tuple (Client IP address, Client
> >    port, Transport Protocol, Server IP address, Server=20
> port) remains the
> >    same.=20
>=20
>   I think it's best to simply delete that paragraph.
>=20
> > T5. The last paragraph in 2.6.1:=20
> >=20
> >>   The above requirement is necessary, but not sufficient=20
> in all cases.
> >    Other specifications give additional situations where=20
> the packet is
> >    to be considered as a new request.  Those=20
> recommendations MUST also
> >    be followed.
> >=20
> > Having a MUST requirement over undefined 'other=20
> specification' is not=20
> > implementable. I would suggest to either clarify what are=20
> these 'other=20
> > specifications' or take this out.
>=20
>   OK.  I'll delete it.
>=20
> > E1. Please expand TLS at first occurrence.=20
>=20
>   Done.
>=20
> > E2. The Introduction section speaks about 'the default Internet MTU=20
> > (576). Strictly speaking this value is not standardized in=20
> any place,
>=20
>   That should be the "common Internet MTU".  The text could say:
>=20
> These packets are larger than the common Internet MTU (576),=20
> resulting in fragmentation of the packets at the IP layer=20
> when they are proxied over the Internet.
>=20
> > and later in section 1.1 reference is made to RADIUS packets being=20
> > restricted to 1500 octets in size. Looks like an unnecessary=20
> > inconsistency.
>=20
>   That is for a different use-case.  I can update that text to say:
>=20
> For example, where EAP-TLS authentication [RFC5216] is=20
> attempted and both the EAP peer and server utilize=20
> certificate chains of 8KB, as many as 15 round-trips can be=20
> required if RADIUS packets are restricted to the common=20
> Ethernet MTU (1500 octets) for EAP over LAN (EAPoL) use-cases.
>=20
> > E3. Section 1.2 - the syntax in the RADIUS server definition is=20
> > inconsistent with the syntax of the rest of the definitions
>=20
>   OK.  That could say:
>=20
> A device that provides one or more of authentication,=20
> authorization, and/or accounting (AAA) services to a NAS.
>=20
>=20
> > E4. Section 2.6.7:=20
> >=20
> >>  We RECOMMEND that implementors of this specification
> >    familiarize themselves with TCP application programming=20
> concepts.  We
> >    RECOMMEND also that existing TCP applications be=20
> examined with an eye
> >    to robustness, performance, scalability, etc.
> >=20
> > The use of capitalized (a la 2119) keywords in a=20
> personalized phrase=20
> > does not make much sense. RECOMMEND is not a keyword actually. I=20
> > suggest rephrasing.
>=20
>   Changed to: "It is RECOMMENDED that..."
>=20
>   If this looks OK, I'll issue an updated draft tomorrow.
>=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: Tue, 27 Apr 2010 05:59:00 +0000
Message-ID: <BLU137-W322E5875A303DFF9F9694593030@phx.gbl>
Content-Type: multipart/alternative; boundary="_be14ca7d-4a49-409b-8db1-1b519be1d0b9_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
CC: <mail@stefan-winter.de>
Subject: Review of "TLS Encryption for RADIUS" (Experimental)  (part I, Technical)
Date: Mon, 26 Apr 2010 22:57:58 -0700
MIME-Version: 1.0

--_be14ca7d-4a49-409b-8db1-1b519be1d0b9_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


   2.  negotiate TLS sessions according to [RFC5246] or its predecessor
       TLS 1.1.  The following restrictions apply:

       *  The authentication MUST be mutual=2C i.e. both the RADIUS/TLS
          server and the RADIUS/TLS client authenticate each other.

       *  The client MUST NOT negotiate cipher suites which only provide
          integrity protection.

       *  The TLS session MAY use mutual PSKs for connection setup.

       *  Negotiation of compression for the TLS session is OPTIONAL.

       *  RADIUS/TLS implementations MUST support the mandatory to
          implement cipher suites specified in TLS (i.e.
          TLS_RSA_WITH_3DES_EDE_CBC_SHA).  For purposes of compatibility
          with some current deployments implementations SHOULD support
          TLS_RSA_WITH_RC4_128_SHA and TLS_RSA_WITH_AES_128_CBC_SHA as
          well (see Section 3.2 (1) ).

[BA] Several issues with this:

a.  There is no statement about mandatory to implement TLS version (e.g. MU=
ST
support TLS 1.0 and later). =20

b. There is no statement about mandatory to implement authentication mechan=
ism
(e.g. mutual TLS with certificates). =20

Recommend re-writing as follows:

"  2.  negotiate TLS sessions.  The following restrictions apply:

       *  Support for TLS v1.1 [RFC4346] or later (e.g. TLS 1.2 [RFC5246]) =
is REQUIRED.=20

       *  Support for compression is OPTIONAL.=20

       *  Support for certificate-based mutual authentication is REQUIRED.=
=20

       *  Support for TLS-PSK mutual authentication [RFC4279] is OPTIONAL. =
=20

       *  Negotiation of mutual authentication is REQUIRED.=20

       *  Negotiation of a ciphersuite providing for confidentiality as wel=
l
          as integrity protection is REQUIRED. =20

       *  RADIUS/TLS nodes MUST NOT negotiate ciphersuites with NULL encryp=
tion (e.g. [RFC4785]). =20

       *  Negotiation of compression is OPTIONAL.

       *  RADIUS/TLS implementations MUST at a minimum support negotiation
          of the TLS_RSA_WITH_3DES_EDED_CBC_SHA ciphersuite=2C and SHOULD
          support TLS_RSA_WITH_RC4_128_SHA and TLS_RSA_WITH_AES_128_CBC_SHA=
 as
          well (see Section 3.2 (1) ).

       *  In addition=2C RADIUS/TLS implementations MUST support negotiatio=
n of
          the mandatory-to-implement ciphersuites required by the versions =
of TLS
          that they support." =20



       *  Certificate validation MUST include the verification rules as
          per [RFC5280]=2C using information from trusted sources only
          (e.g. locally configured names).  If service names as per
          [RFC4985] are present in the certificate and dynamic discovery
          utilizing SRVs in DNS is used (see
          [I-D.winter-dynamic-discovery]) and the TLS implementation
          supports evaluation of the extensions in [RFC4985]=2C the SRV
          entry MUST be validated.  In cases where no DNS SRV resolution
          took place to arrive at the TLS peer=2C subjectAltName:SRV
          entries can be ignored.


[BA]  I'm not clear what "using information from trusted sources only"
means=2C exactly.=20

Given the MUST here=2C the reference to dynamic discovery is probably
normative.  My suggestion is to move this material to the dynamic discovery
draft so as to remove the normative dependency. =20

Among other things=2C moving this to the dynamic discovery document will
provide some additional time to think through the security issues. =20

Use of the extensions in [RFC4985] does not necessarily address the
problem of forgery of DNS SRV RRs unless some kind of name constraint is al=
so
applied.  For example=2C an attacker could forge an SRV RR that indicates t=
hat the
RADIUS/TLS server for example.com is hosted with the evilhacker.com domain=
=2C and
the fradulent RADIUS/TLS server could provide a valid certificate with a
service extenion indicating its acting as the RADIUS/TLS server for example=
.com.=20
The problem is that the certificate chain will not include a trust anchor w=
ithin
the example.com domain. =20

2.3. Connecting Client Identity

   In RADIUS/UDP=2C 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=2C it also does not permit to determine
   whether there is more than one entity connecting from the same IP
   address.

[BA] The NAS is identified by the NAS-Identifier/NAS-IP-Address/NAS-IPv6-Ad=
dress
attributes=2C no?  Since RADIUS identifies entities by IP address=2C by
definition all packets originating from a given IP address are assumed
to come from the same entity.  Suggest rewriting as follows:

 " In RADIUS/UDP=2C clients are uniquely identified by their IP address.
   Since the shared secret is associated with the origin IP address=2C=20
   if more than one RADIUS client is associated with the same IP
   address=2C then those clients also must utilize the same shared secret=
=2C
   a practice which is inherently insecure as noted in [RFC5247]."


   RADIUS/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=2C it permits 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/TLS should expose as many details of the
   TLS connection which belongs to an incoming RADIUS packet as possible
   to the application layer to allow the administrator to define the
   identification criteria which are applicable to his desired
   operational model.  In X.509 certificate operation=2C 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=2C at least the following parameters of the TLS
   connection should be exposed:

   o  Originating IP address

   o  TLS Identifier

[BA] It seems to me that the above text is somewhat too vague in that it do=
esn't
precisely define what parameters should be used to differentiate RADIUS cli=
ents
and servers from each other.=20

2.4. RADIUS Datagrams

   Authentication=2C Accounting and Authorization packets are sent
   according to the following rules:

   RADIUS/TLS clients handle the following packet types from [RFC2865]=2C
   [RFC2866]=2C [RFC5176] on the connection they initiated (see
   Section 3.3 (3) and (4) ):

   o  send Access-Request

   o  send Accounting-Request

   o  send Status-Server

   o  send Disconnect-ACK

   o  send Disconnect-NAK

   o  send CoA-ACK

   o  send CoA-NAK

   o  receive Access-Challenge

   o  receive Access-Accept

   o  receive Access-Reject

   o  receive Accounting-Response

   o  receive Disconnect-Request

   o  receive CoA-Request

   RADIUS/TLS servers handle the following packet types from [RFC2865]=2C
   [RFC2866]=2C [RFC5176] on the connections they serve to clients:

   o  receive Access-Request

   o  receive Accounting-Request

   o  receive Status-Server

   o  receive Disconnect-ACK

   o  receive Disconnect-NAK

   o  receive CoA-ACK

   o  receive CoA-NAK

   o  send Access-Challenge

   o  send Access-Accept

   o  send Access-Reject

   o  send Accounting-Response

   o  send Disconnect-Request

   o  send CoA-Request

[BA] This assumes that the RADIUS server is also a Dynamic Authorization Cl=
ient.  This is not=20
necessarily the case.   CoA-Request and Disconnect-Request packets can also=
 be sent by a=20
DAC that originates its own TLS connection=2C no?=20

My suggestion is that you separate the DAC/DAS roles from the RADIUS client=
/server roles in this
section.  I'd also note that the RADIUS over TCP document does not recommen=
d that Dynamic
Authorization traffic be sent over TLS. =20
 		 	   		  =

--_be14ca7d-4a49-409b-8db1-1b519be1d0b9_
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'>
&nbsp=3B&nbsp=3B 2.&nbsp=3B negotiate TLS sessions according to [RFC5246] o=
r its predecessor<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B TLS 1=
.1.&nbsp=3B The following restrictions apply:<br><br>&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B The authentication MUST be mutual=2C =
i.e. both the RADIUS/TLS<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B server and the RADIUS/TLS client authenticate e=
ach other.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=
=3B The client MUST NOT negotiate cipher suites which only provide<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B integri=
ty protection.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nb=
sp=3B The TLS session MAY use mutual PSKs for connection setup.<br><br>&nbs=
p=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Negotiation of compr=
ession for the TLS session is OPTIONAL.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbs=
p=3B&nbsp=3B&nbsp=3B *&nbsp=3B RADIUS/TLS implementations MUST support the =
mandatory to<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B implement cipher suites specified in TLS (i.e.<br>&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B TLS_RSA_WITH_=
3DES_EDE_CBC_SHA).&nbsp=3B For purposes of compatibility<br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B with some curre=
nt deployments implementations SHOULD support<br>&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B TLS_RSA_WITH_RC4_128_SHA and=
 TLS_RSA_WITH_AES_128_CBC_SHA as<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B well (see Section 3.2 (1) ).<br><br>[BA=
] Several issues with this:<br><br>a.&nbsp=3B There is no statement about m=
andatory to implement TLS version (e.g. MUST<br>support TLS 1.0 and later).=
 &nbsp=3B<br><br>b. There is no statement about mandatory to implement auth=
entication mechanism<br>(e.g. mutual TLS with certificates). &nbsp=3B<br><b=
r>Recommend re-writing as follows:<br><br>"&nbsp=3B 2.&nbsp=3B negotiate TL=
S sessions.&nbsp=3B The following restrictions apply:<br><br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Support for TLS v1.1 [RFC4346=
] or later (e.g. TLS 1.2 [RFC5246]) is REQUIRED. <br><br>&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Support for compression is OPTIONA=
L. <br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Suppo=
rt for certificate-based mutual authentication is REQUIRED. <br><br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Support for TLS-PSK m=
utual authentication [RFC4279] is OPTIONAL. &nbsp=3B<br><br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Negotiation of mutual authent=
ication is REQUIRED. <br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B *&nbsp=3B Negotiation of a ciphersuite providing for confidentiality as=
 well<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B as integrity protection is REQUIRED. &nbsp=3B<br><br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B RADIUS/TLS nodes MUST NOT neg=
otiate ciphersuites with NULL encryption (e.g. [RFC4785]). &nbsp=3B<br><br>=
&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Negotiation of c=
ompression is OPTIONAL.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbs=
p=3B *&nbsp=3B RADIUS/TLS implementations MUST at a minimum support negotia=
tion<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B of the TLS_RSA_WITH_3DES_EDED_CBC_SHA ciphersuite=2C and SHOULD<br>&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B supp=
ort TLS_RSA_WITH_RC4_128_SHA and TLS_RSA_WITH_AES_128_CBC_SHA as<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B well (s=
ee Section 3.2 (1) ).<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B *&nbsp=3B In addition=2C RADIUS/TLS implementations MUST support negoti=
ation of<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B the mandatory-to-implement ciphersuites required by the version=
s of TLS<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B that they support." &nbsp=3B<br><br><br><br>&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B *&nbsp=3B Certificate validation MUST include=
 the verification rules as<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B per [RFC5280]=2C using information from trusted=
 sources only<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B (e.g. locally configured names).&nbsp=3B If service names as=
 per<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B [RFC4985] are present in the certificate and dynamic discovery<br>&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B utili=
zing SRVs in DNS is used (see<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B [I-D.winter-dynamic-discovery]) and the TLS =
implementation<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&=
nbsp=3B&nbsp=3B supports evaluation of the extensions in [RFC4985]=2C the S=
RV<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B entry MUST be validated.&nbsp=3B In cases where no DNS SRV resolution<b=
r>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B =
took place to arrive at the TLS peer=2C subjectAltName:SRV<br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B entries can be =
ignored.<br><br><br>[BA]&nbsp=3B I'm not clear what "using information from=
 trusted sources only"<br>means=2C exactly. <br><br>Given the MUST here=2C =
the reference to dynamic discovery is probably<br>normative.&nbsp=3B My sug=
gestion is to move this material to the dynamic discovery<br>draft so as to=
 remove the normative dependency. &nbsp=3B<br><br>Among other things=2C mov=
ing this to the dynamic discovery document will<br>provide some additional =
time to think through the security issues. &nbsp=3B<br><br>Use of the exten=
sions in [RFC4985] does not necessarily address the<br>problem of forgery o=
f DNS SRV RRs unless some kind of name constraint is also<br>applied.&nbsp=
=3B For example=2C an attacker could forge an SRV RR that indicates that th=
e<br>RADIUS/TLS server for example.com is hosted with the evilhacker.com do=
main=2C and<br>the fradulent RADIUS/TLS server could provide a valid certif=
icate with a<br>service extenion indicating its acting as the RADIUS/TLS se=
rver for example.com. <br>The problem is that the certificate chain will no=
t include a trust anchor within<br>the example.com domain. &nbsp=3B<br><br>=
2.3. Connecting Client Identity<br><br>&nbsp=3B&nbsp=3B In RADIUS/UDP=2C cl=
ients are uniquely identified by their IP address.<br>&nbsp=3B&nbsp=3B This=
 does not permit to determine whether the connecting entity is a<br>&nbsp=
=3B&nbsp=3B NAS or a different server which proxies a request.&nbsp=3B When=
 NAT is used<br>&nbsp=3B&nbsp=3B on the path to the server=2C it also does =
not permit to determine<br>&nbsp=3B&nbsp=3B whether there is more than one =
entity connecting from the same IP<br>&nbsp=3B&nbsp=3B address.<br><br>[BA]=
 The NAS is identified by the NAS-Identifier/NAS-IP-Address/NAS-IPv6-Addres=
s<br>attributes=2C no?&nbsp=3B Since RADIUS identifies entities by IP addre=
ss=2C by<br>definition all packets originating from a given IP address are =
assumed<br>to come from the same entity.&nbsp=3B Suggest rewriting as follo=
ws:<br><br>&nbsp=3B" In RADIUS/UDP=2C clients are uniquely identified by th=
eir IP address.<br>&nbsp=3B&nbsp=3B Since the shared secret is associated w=
ith the origin IP address=2C <br>&nbsp=3B&nbsp=3B if more than one RADIUS c=
lient is associated with the same IP<br>&nbsp=3B&nbsp=3B address=2C then th=
ose clients also must utilize the same shared secret=2C<br>&nbsp=3B&nbsp=3B=
 a practice which is inherently insecure as noted in [RFC5247]."<br><br><br=
>&nbsp=3B&nbsp=3B RADIUS/TLS makes it possible to preserve this traditional=
 RADIUS<br>&nbsp=3B&nbsp=3B semantics by identifying a connecting client by=
 the IP address which<br>&nbsp=3B&nbsp=3B initiated the TLS connection.&nbs=
p=3B In addition=2C it permits a much more<br>&nbsp=3B&nbsp=3B fine-grained=
 identification.&nbsp=3B The parameters of the TLS connection<br>&nbsp=3B&n=
bsp=3B can be attributed to the RADIUS packets inside the TLS connection.<b=
r>&nbsp=3B&nbsp=3B An implementation of RADIUS/TLS should expose as many de=
tails of the<br>&nbsp=3B&nbsp=3B TLS connection which belongs to an incomin=
g RADIUS packet as possible<br>&nbsp=3B&nbsp=3B to the application layer to=
 allow the administrator to define the<br>&nbsp=3B&nbsp=3B identification c=
riteria which are applicable to his desired<br>&nbsp=3B&nbsp=3B operational=
 model.&nbsp=3B In X.509 certificate operation=2C at least the<br>&nbsp=3B&=
nbsp=3B following parameters of the TLS connection should be exposed:<br><b=
r>&nbsp=3B&nbsp=3B o&nbsp=3B Originating IP address<br><br>&nbsp=3B&nbsp=3B=
 o&nbsp=3B Certificate Fingerprint<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B Issuer=
<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B Subject<br><br>&nbsp=3B&nbsp=3B o&nbsp=
=3B all X509v3 Extended Key Usage<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B all X50=
9v3 Subject Alternative Name<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B all X509v3 C=
ertificate Policies<br><br>&nbsp=3B&nbsp=3B In TLS-PSK operation=2C at leas=
t the following parameters of the TLS<br>&nbsp=3B&nbsp=3B connection should=
 be exposed:<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B Originating IP address<br><b=
r>&nbsp=3B&nbsp=3B o&nbsp=3B TLS Identifier<br><br>[BA] It seems to me that=
 the above text is somewhat too vague in that it doesn't<br>precisely defin=
e what parameters should be used to differentiate RADIUS clients<br>and ser=
vers from each other. <br><br>2.4. RADIUS Datagrams<br><br>&nbsp=3B&nbsp=3B=
 Authentication=2C Accounting and Authorization packets are sent<br>&nbsp=
=3B&nbsp=3B according to the following rules:<br><br>&nbsp=3B&nbsp=3B RADIU=
S/TLS clients handle the following packet types from [RFC2865]=2C<br>&nbsp=
=3B&nbsp=3B [RFC2866]=2C [RFC5176] on the connection they initiated (see<br=
>&nbsp=3B&nbsp=3B Section 3.3 (3) and (4) ):<br><br>&nbsp=3B&nbsp=3B o&nbsp=
=3B send Access-Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send Accounting-R=
equest<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send Status-Server<br><br>&nbsp=3B=
&nbsp=3B o&nbsp=3B send Disconnect-ACK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B se=
nd Disconnect-NAK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send CoA-ACK<br><br>&nb=
sp=3B&nbsp=3B o&nbsp=3B send CoA-NAK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B rece=
ive Access-Challenge<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Access-Accep=
t<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Access-Reject<br><br>&nbsp=3B&n=
bsp=3B o&nbsp=3B receive Accounting-Response<br><br>&nbsp=3B&nbsp=3B o&nbsp=
=3B receive Disconnect-Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Co=
A-Request<br><br>&nbsp=3B&nbsp=3B RADIUS/TLS servers handle the following p=
acket types from [RFC2865]=2C<br>&nbsp=3B&nbsp=3B [RFC2866]=2C [RFC5176] on=
 the connections they serve to clients:<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B r=
eceive Access-Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Accounting-=
Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive Status-Server<br><br>&nbs=
p=3B&nbsp=3B o&nbsp=3B receive Disconnect-ACK<br><br>&nbsp=3B&nbsp=3B o&nbs=
p=3B receive Disconnect-NAK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive CoA-A=
CK<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B receive CoA-NAK<br><br>&nbsp=3B&nbsp=
=3B o&nbsp=3B send Access-Challenge<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send =
Access-Accept<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send Access-Reject<br><br>&=
nbsp=3B&nbsp=3B o&nbsp=3B send Accounting-Response<br><br>&nbsp=3B&nbsp=3B =
o&nbsp=3B send Disconnect-Request<br><br>&nbsp=3B&nbsp=3B o&nbsp=3B send Co=
A-Request<br><br>[BA] This assumes that the RADIUS server is also a Dynamic=
 Authorization Client.&nbsp=3B This is not <br>necessarily the case.&nbsp=
=3B&nbsp=3B CoA-Request and Disconnect-Request packets can also be sent by =
a <br>DAC that originates its own TLS connection=2C no? <br><br>My suggesti=
on is that you separate the DAC/DAS roles from the RADIUS client/server rol=
es in this<br>section.&nbsp=3B I'd also note that the RADIUS over TCP docum=
ent does not recommend that Dynamic<br>Authorization traffic be sent over T=
LS.&nbsp=3B <br> 		 	   		  </body>
</html>=

--_be14ca7d-4a49-409b-8db1-1b519be1d0b9_--

--
to unsubscribe send a message to radiusext-request@ops.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, 26 Apr 2010 20:47:30 +0000
Message-ID: <4BD5FBB3.7070104@deployingradius.com>
Date: Mon, 26 Apr 2010 22:46:43 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: 'Stefan Winter' <mail@stefan-winter.de>, radiusext@ops.ietf.org
Subject: Re: RADEXT WG Last Call on "TLS Encryption for RADIUS" (Experimental)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> I am starting work on a PROTO writeup for this document, on the assumption
> that "lack of response implies consent".  If any issues become apparent 
> in the course of that review, I'll post them to the list. 
> 
> While that's in progress,  WG participants are encouraged to:
> 
> a. Read the document, and post any thoughts to the list (even if that is
> only
> "the document appears ready"); 
> b. Continue to make progress on closing issues within dependency documents 
> (e.g. RADIUS over TCP, Status-Server); 
> c. Post updates on implementation progress; 

  My comments are editorial only.

>...
>  There are multiple known attacks on the MD5 algorithm
>...

  Adding reference(s) would be good.  These can be lifted from RFC 3579,
among others.

>...
>      These middleboxes may learn privacy-
>   relevant data while forwarding requests.
>...

  RADIUS over TLS doesn't solve this problem.  It's still "hop by hop",
and doesn't create "end to end" security.  The use of proxies is still
useful in many environments, and those proxies still have access to all
of the privacy-relevant data.

>...
>   1.  establish TCP connections as per ...
>
>   2.  negotiate TLS sessions according to [RFC5246] or its predecessor
>       TLS 1.1.
>...

  It would be good to note that there is no RADIUS equivalent of
"starttls".  A client and server is marked either as "supporting TLS",
or "not supporting TLS".  So the client/server just "starts TLS" if TLS
is supported.

  i.e. the above text could be understood as "negotiate TLS version and
features", and not "negotiate whether or not to use TLS".

  It may be sufficient to note that step (1) MUST be immediately
followed by step (2), and "bare TCP" on port 2083 MUST NOT be used.


>...
>   In RADIUS/UDP, clients are uniquely identified by their IP address.
>   This does not permit to determine when
>...

  English: This *what* ..

  And elsewhere in the document.  The word "this" should usually be
followed by a specifier, e.g. noun.

  and: Does not permit *who* to determine...?


>...
>3.2.  Ciphersuites and Compression Negotiation Considerations
>
>   Not all TLS ciphersuites in [RFC5246] are supported by available TLS
>   tool kits, and licenses may be required in some cases.  The existing
>   implementations of RADIUS/TLS use OpenSSL as cryptographic backend,
>   which supports all of the ciphersuites listed in the rules in the
>   normative section.
>..

  The implementation text could be put into an "implementation notes"
section.  But it's not serious.

>...
>   (1) After the TLS session is established, RADIUS packet payloads are
>   exchanged over the encrypted TLS tunnel.  In RADIUS/UDP, the packet
>   size can be determined by evaluating the size of the datagram that
>   arrived.  Due to the stream nature of TCP and TLS, this does not >hold
>   true for RADIUS/TLS packet exchange.  Instead, packet boundaries of
>   RADIUS packets that arrive in the stream are calculated by >evaluating
>   the packet's Length field.  Special care needs to be taken on the
>   packet sender side that the value of the Length field is indeed
>   correct before sending it over the TLS tunnel, because incorrect
>   packet lengths can no longer be detected by a differing datagram
>   boundary.
>...

  Adding a reference to RADIUS over TCP, Section 2.6.4 may be good.  It
outlines these issues in more detail.

>...
>   If a given IP device is able to receive RADIUS payloads on multiple
>   transports, this may or may not be the same instance of software,
>and
>   it may or may not serve the same purposes.  It is not safe to assume
>   that both ports are interchangeable.  In particular, it can not be
>   assumed that state is maintained for the packet payloads between the
>   transports.  Two such instances MUST be considered separate RADIUS
>   server entities.
>...

  Ideally, this text should be similar between this doc, the TCP doc,
and the DTLS doc.  I'll take a look at regularizing some of it.

>...
>   If peer communication between two devices is configured for both
>   RADIUS/TLS and RADIUS/UDP, a failover from TLS security to classic
>   RADIUS security opens the way for a down-bidding attack if an
>   adversary can maliciously close the TCP connection, or prevent it
>   from being established.  In this case, security of the packet
> payload
>   is reduced from the selected TLS cipher suite packet encryption to
>   the classic MD5 per-attribute encryption.
>...

  It may be worth discussing how to address that issue.  i.e. both
transports SHOULD be configured only temporarily, as part of a migration
strategy.  Once a secure transport is available, the RADIUS/UDP method
SHOULD be deprecated.  This issue is easier for the TCP document, where
no security means bidding-down isn't an issue.  It's also the subject of
much discussion in the DTLS draft, which re-uses the same server port &&
transport, so bidding-down needs to be handled very carefully.


Nits: the document uses the terms RADIUS/UDP, RADIUS/TCP, and
RADIUS/TLS.  These are not consistent with the TCP or DTLS documents.
It would be good to make all of these consistent across the documents.

  Does the WG have a preference for *which* terminology to use?

  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, 26 Apr 2010 17:49:23 +0000
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 26 Apr 2010 19:49:00 +0200
Subject: Re: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
From: Wojciech Dec <wdec@cisco.com>
To: Peter Deacon <peterd@iea-software.com>
CC: <radiusext@ops.ietf.org>
Message-ID: <C7FB9EAC.33CF%wdec@cisco.com>
Thread-Topic: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Thread-Index: AcrlaMBacINmIXU5aUGJvRf7FcLf+w==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit

Hello Peter,


On 26/04/2010 19:37, "Peter Deacon" <peterd@iea-software.com> wrote:

> On Mon, 26 Apr 2010, Wojciech Dec (wdec) wrote:
> 
>> Hello Peter,
>> As part of the resolution of Issue 335, we're proposing the addition of
>> the following text/section into the draft. Please let us know if this is
>> satisfactory.
> 
>> "Syntactically, the Framed-IPv6-Address and the RFC3162
>> Framed-IPv6-Prefix attributes are identical. In terms of their intended
>> semantics however the former represents a statefully assigned IPv6
>> address while the latter a prefix intended for application on a target
>> interface and are envisaged to be used in co-existence. Thus, in order
>> to preserve this semantical distinction it is recommended that each
>> attribute be used for its intended purpose, with the functional
>> substitution of one attribute for the other being an optional
>> configuration feature of a Radius client."
> 
> Hi Woj,
> 
> For Accounting messages in only the narrow case where Framed-IPv6-Address
> is assigned and no prefix is ultimatly allocated to the user what do you
> think about a recommendation for the /128 prefix be sent as well?

Yes, I would expect this to be already captured in the attribute usage
section/table with the 0+ notation. It's my understanding that the inclusion
of such optional Radius attributes is always made configurable.

> 
> Regardless your text works for me as-is, thank you.
>
Thanks,
Woj. 
> regards,
> Peter
> 
>> Thanks,
>> Woj.
> 
>>> -----Original Message-----
>>> From: Peter Deacon [mailto:peterd@iea-software.com]
>>> Sent: 03 March 2010 21:19
>>> To: Wojciech Dec (wdec)
>>> Cc: radiusext@ops.ietf.org
>>> Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access
>>> Networks
>>> 
>>> On Wed, 3 Mar 2010, Wojciech Dec (wdec) wrote:
>>> 
>>>>> My suggestion WRT an accounting restriction is based on a scenario:
>>>>> Accounting system relies on RFC 3162 to report client IP.
>>> 
>>>>> NAS decides to send IPv6-Framed-Address rather than RFC 3162
>> method.
>>>>> Accounting system requires modification to continue to
>>>>> understand the same information.
>>> 
>>>> Yes, I see your point. Don't you think however that this could be
>>>> handled by a client knob/implementation? I.E. If in an access-accept
>>> a
>>>> server sends the IPv6-Framed-Address, then the NAS client can
>>> interpret
>>>> it to mean that its ok to use this attribute in accounting messages.
>>> If
>>> 
>>>> an IPv6-Framed-Address does not come down in an access-accept, then
>>> the
>>>> NAS would use by default "whatever it uses today", unless it has
>> been
>>>> explicitly configured to send accounting info with using
>>>> IPv6-Framed-Address.
>>> 
>>>> This would seem to cover your concerns. What do you think?
>>> 
>>> Yes, sounds reasonable.
>>> 
>>> regards,
>>> Peter
>> 


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 26 Apr 2010 17:38:31 +0000
Date: Mon, 26 Apr 2010 10:37:56 -0700 (Pacific Daylight Time)
From: Peter Deacon <peterd@iea-software.com>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>
cc: radiusext@ops.ietf.org
Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Message-ID: <alpine.WNT.2.00.1004260932320.2388@SMURF>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII

On Mon, 26 Apr 2010, Wojciech Dec (wdec) wrote:

> Hello Peter,
> As part of the resolution of Issue 335, we're proposing the addition of
> the following text/section into the draft. Please let us know if this is
> satisfactory.

> "Syntactically, the Framed-IPv6-Address and the RFC3162
> Framed-IPv6-Prefix attributes are identical. In terms of their intended
> semantics however the former represents a statefully assigned IPv6
> address while the latter a prefix intended for application on a target
> interface and are envisaged to be used in co-existence. Thus, in order
> to preserve this semantical distinction it is recommended that each
> attribute be used for its intended purpose, with the functional
> substitution of one attribute for the other being an optional
> configuration feature of a Radius client."

Hi Woj,

For Accounting messages in only the narrow case where Framed-IPv6-Address 
is assigned and no prefix is ultimatly allocated to the user what do you 
think about a recommendation for the /128 prefix be sent as well?

Regardless your text works for me as-is, thank you.

regards,
Peter

> Thanks,
> Woj.

>> -----Original Message-----
>> From: Peter Deacon [mailto:peterd@iea-software.com]
>> Sent: 03 March 2010 21:19
>> To: Wojciech Dec (wdec)
>> Cc: radiusext@ops.ietf.org
>> Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access
>> Networks
>>
>> On Wed, 3 Mar 2010, Wojciech Dec (wdec) wrote:
>>
>>>> My suggestion WRT an accounting restriction is based on a scenario:
>>>> Accounting system relies on RFC 3162 to report client IP.
>>
>>>> NAS decides to send IPv6-Framed-Address rather than RFC 3162
> method.
>>>> Accounting system requires modification to continue to
>>>> understand the same information.
>>
>>> Yes, I see your point. Don't you think however that this could be
>>> handled by a client knob/implementation? I.E. If in an access-accept
>> a
>>> server sends the IPv6-Framed-Address, then the NAS client can
>> interpret
>>> it to mean that its ok to use this attribute in accounting messages.
>> If
>>
>>> an IPv6-Framed-Address does not come down in an access-accept, then
>> the
>>> NAS would use by default "whatever it uses today", unless it has
> been
>>> explicitly configured to send accounting info with using
>>> IPv6-Framed-Address.
>>
>>> This would seem to cover your concerns. What do you think?
>>
>> Yes, sounds reasonable.
>>
>> regards,
>> Peter
>

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 26 Apr 2010 16:56:41 +0000
Message-ID: <4BD5C58D.6040303@deployingradius.com>
Date: Mon, 26 Apr 2010 18:55:41 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
CC: radiusext@ops.ietf.org
Subject: Re: AD review of draft-ietf-radext-tcp-transport-05
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Romascanu, Dan (Dan) wrote:
> The issues are divided into Technical (T) and Editorial (E). 
> 
> T1. The document is marked as EXPERIMENTAL. It would be useful if it
> mentions in one of the introductory sections what are the goals and
> limitations (if any) of the experimental deployment and what would be
> the success criteria of the experiment that would allow for taking the
> document to the standards track later. 

  Suggested text for Section 1 (Introduction).  Move the last paragraph
from Section 1.2 to higher up in the document, and add some text:

...
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 additional
confidentiality and security) is NOT RECOMMENDED, as there has been
little or no operational experience with it.

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

> T2. Section 2.2: 
> 
>>  Since these ports are unused by existing RADIUS implementations, the
>    assigned values SHOULD be used as the default ports for RADIUS over
>    TCP.
> 
> Why is this a SHOULD and not a MUST? 

  No reason...  I'll change it.

> T3. Section 2.3 needs a complete re-writing: 
...
> The correct solution is for the MIB documents to be updated in the
> future with new MIB objects of appropriate syntax. For the time being
> the only thing that this section should say is that the MIB modules do
> not support RADIUS over TCP and that they will need to be updated in the
> future. 

  Suggest replacing the text in 2.3 with:

The MIB Module definitions in [RFC4668], [RFC4669], [RFC4670],
[RFC4671], [RFC4672], and [RFC4673] are intended to be used for RADIUS
over UDP.  As such, they do not support RADIUS over TCP, and will need
to be updated in the future.  Implementations of RADIUS over TCP
SHOULD NOT re-use these MIB Modules to perform statistics counting for
RADIUS over TCP connections.

> T4. The following section in 2.6.1 is confusing: 
> 
>>  Much of the discussion in this section can be summarized by the
>    following requirement.  RADIUS requests MAY be re-transmitted
>    verbatim only if the following 5-tuple (Client IP address, Client
>    port, Transport Protocol, Server IP address, Server port) remains the
>    same. 

  I think it's best to simply delete that paragraph.

> T5. The last paragraph in 2.6.1: 
> 
>>   The above requirement is necessary, but not sufficient in all cases.
>    Other specifications give additional situations where the packet is
>    to be considered as a new request.  Those recommendations MUST also
>    be followed.
> 
> Having a MUST requirement over undefined 'other specification' is not
> implementable. I would suggest to either clarify what are these 'other
> specifications' or take this out. 

  OK.  I'll delete it.

> E1. Please expand TLS at first occurrence. 

  Done.

> E2. The Introduction section speaks about 'the default Internet MTU
> (576). Strictly speaking this value is not standardized in any place,

  That should be the "common Internet MTU".  The text could say:

These packets are larger than the common
Internet MTU (576), resulting in fragmentation of the packets at the
IP layer when they are proxied over the Internet.

> and later in section 1.1 reference is made to RADIUS packets being
> restricted to 1500 octets in size. Looks like an unnecessary
> inconsistency. 

  That is for a different use-case.  I can update that text to say:

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 the common Ethernet MTU (1500 octets) for EAP over
LAN (EAPoL) use-cases.

> E3. Section 1.2 - the syntax in the RADIUS server definition is
> inconsistent with the syntax of the rest of the definitions

  OK.  That could say:

A device that provides one or more of authentication, authorization,
and/or accounting (AAA) services to a NAS.


> E4. Section 2.6.7: 
> 
>>  We RECOMMEND that implementors of this specification
>    familiarize themselves with TCP application programming concepts.  We
>    RECOMMEND also that existing TCP applications be examined with an eye
>    to robustness, performance, scalability, etc.
> 
> The use of capitalized (a la 2119) keywords in a personalized phrase
> does not make much sense. RECOMMEND is not a keyword actually. I suggest
> rephrasing. 

  Changed to: "It is RECOMMENDED that..."

  If this looks OK, I'll issue an updated draft tomorrow.

--
to unsubscribe send a message to radiusext-request@ops.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, 26 Apr 2010 10:49:16 +0000
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Date: Mon, 26 Apr 2010 12:48:24 +0200
Message-ID: <A16B9A4922C4A544A94565E870362B5001C5D034@XMB-AMS-111.cisco.com>
Thread-Topic: RADEXT WG last call on RADIUS attributes for IPv6 Access Networks
Thread-Index: Acq7Dr64kyHowWg8Q7CO9Gzt/0sSEAqHeqnw
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Peter Deacon" <peterd@iea-software.com>
Cc: <radiusext@ops.ietf.org>

Hello Peter,

As part of the resolution of Issue 335, we're proposing the addition of
the following text/section into the draft. Please let us know if this is
satisfactory.

"Syntactically, the Framed-IPv6-Address and the RFC3162
Framed-IPv6-Prefix attributes are identical. In terms of their intended
semantics however the former represents a statefully assigned IPv6
address while the latter a prefix intended for application on a target
interface and are envisaged to be used in co-existence. Thus, in order
to preserve this semantical distinction it is recommended that each
attribute be used for its intended purpose, with the functional
substitution of one attribute for the other being an optional
configuration feature of a Radius client."

Thanks,
Woj.



> -----Original Message-----
> From: Peter Deacon [mailto:peterd@iea-software.com]
> Sent: 03 March 2010 21:19
> To: Wojciech Dec (wdec)
> Cc: radiusext@ops.ietf.org
> Subject: RE: RADEXT WG last call on RADIUS attributes for IPv6 Access
> Networks
>=20
> On Wed, 3 Mar 2010, Wojciech Dec (wdec) wrote:
>=20
> >> My suggestion WRT an accounting restriction is based on a scenario:
> >> Accounting system relies on RFC 3162 to report client IP.
>=20
> >> NAS decides to send IPv6-Framed-Address rather than RFC 3162
method.
> >> Accounting system requires modification to continue to
> >> understand the same information.
>=20
> > Yes, I see your point. Don't you think however that this could be
> > handled by a client knob/implementation? I.E. If in an access-accept
> a
> > server sends the IPv6-Framed-Address, then the NAS client can
> interpret
> > it to mean that its ok to use this attribute in accounting messages.
> If
>=20
> > an IPv6-Framed-Address does not come down in an access-accept, then
> the
> > NAS would use by default "whatever it uses today", unless it has
been
> > explicitly configured to send accounting info with using
> > IPv6-Framed-Address.
>=20
> > This would seem to cover your concerns. What do you think?
>=20
> Yes, sounds reasonable.
>=20
> regards,
> Peter

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 26 Apr 2010 08:27:17 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAE51A.0435A9B3"
Subject: RE: Bernard's notes
Date: Mon, 26 Apr 2010 10:25:22 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402144E5D@307622ANEX5.global.avaya.com>
Thread-Topic: Bernard's notes
Thread-Index: AcrkzbWA2ElDKIglRqKoNvDNBKDqcAAS1KmQ
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_01CAE51A.0435A9B3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Bernard,
=20
Thank you for your status notes. I have two comments:=20
=20
1. Design guidelines - you mention that there are no open IESG DISCUSSes
- this is true, but we should not forget that as discussed previously
because of the rather extensive changes we will need to redo the IESG LC
(may be shorter than the usual four weeks) and redo also the IESG
ballot.=20
=20
2. Alan is holding the pen as editor for all three documents at #1 and
#2. Thanks Alan for doing this - however the chairs may want to consider
a more efficient sharing of the editorial load between the different key
contributors in the future.=20
=20
Dan
=20


________________________________

	From: owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
	Sent: Monday, April 26, 2010 2:17 AM
	To: radiusext@ops.ietf.org
	Subject: Bernard's notes
=09
=09
	Just a note to the WG to summarize where I think we are on
various work items.  The hope is that this note will disclose any
disconnects which could lead to things falling through the cracks.=20
=09
	Issue List (recently updated):
http://www.drizzle.com/~aboba/RADEXT/
=09
	1. Completed IESG Review: Revision Needed
=09
	My notes show two documents in this category:  Design Guidelines
and Status Server.  In both cases, it appears to me that the editor
(Alan DeKok) is holding the token.
=09
	Design Guidelines
=09
	This document currently has no open IESG DISCUSSes.=20
=09
	With respect to Design Guidelines, we have two issues in the
Pending state:  325 and 327.  Alan has updated the draft to -13, and has
posted a request for review of the changes to address both issues.
There is a discussion of Issue 327 in progress.  In the absence of
further discussion on Issue 325, we are going to assume that it has been
resolved.=20
=09
	Next steps: WG participants are requested to review the Design
Guidelines document and post their thoughts to the list:
	http://tools.ietf.org/html/draft-ietf-radext-design
=09
	Status Server
=09
	This document currently has IESG DISCUSS comments open (see
Issue #333), in addition to IETF last call comments (Issue # 330). =20
=09
	Next steps:  The editor need to address the open issues,
preferably by posting a document revision. =20
=09
	2. AD Review:  Revision Needed
=09
	My notes show one document in this category:  RADIUS over TCP,
with the editor (Alan DeKok) holding the token..=20
=09
	There are two open issues relating to the Dan's AD review:
Issues 331 (technical) and 332 (editorial). =20
=09
	Next steps:  The editor needs to address the open issues,
preferably by posting a document revision.=20
=09
	3. Completed RADEXT WG Last Call: Pending PROTO Writeup
=09
	My notes show one document in this category:  Tunnel Type
Values, with Dave Nelson holding the token.=20
=09
	In the past, there had been some discussion about whether RFC
3575 intended to change the IANA allocation process for Tunnel-Type
values to "expert review", even though it did not include RFC 2868 in
the Updates: header.   If so, could an errata if approved make this
document unnecessary (given that an expert review has already been
done)? =20
=09
	Next steps:  Dave Nelson to complete the PROTO writeup.=20
=09
	4. Completed RADEXT WG last call: Revision needed.
=09
	My notes show one document in this category:  IPv6 Access. =20
=09
	There is one issue outstanding from the RADEXT WG last call:
Issue #335.=20
=09
	Next steps:  The editor needs to address the open issues,
preferably by posting a document revision.=20
=09
	5. Completed RADEXT WG last call:  PROTO writeup.=20
=09
	My notes show one document in this category:  RADIUS over TLS.=20
=09
	There are no outstanding issues from RADEXT WG last call.=20
=09
	Next steps:  Bernard Aboba to complete PROTO writeup; RADEXT WG
participants to read the document and post comments to the list.=20
=09
=09
=09
=09
=09
=09
=09


------_=_NextPart_001_01CAE51A.0435A9B3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<META content=3D"MSHTML 6.00.2900.5945" name=3DGENERATOR></HEAD>
<BODY class=3Dhmmessage>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff>Bernard,</FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial =
color=3D#0000ff>Thank you for=20
your status notes. I have two comments: </FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial =
color=3D#0000ff>1. Design=20
guidelines - you mention that there are no open IESG DISCUSSes - this is =
true,=20
but we should not forget that as discussed previously&nbsp;because of =
the rather=20
extensive changes we will need to redo the IESG LC (may be shorter than =
the=20
usual four weeks) and redo also the IESG ballot. </FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial =
color=3D#0000ff>2. Alan is=20
holding the pen as editor for all three documents at #1 and #2. Thanks =
Alan for=20
doing this -&nbsp;however the chairs may want to consider a more =
efficient=20
sharing of the editorial load between the different key contributors in =
the=20
future. </FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff>Dan</FONT></SPAN></DIV>
<DIV><SPAN class=3D728201808-26042010><FONT face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma><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> Monday, April 26, 2010 2:17 AM<BR><B>To:</B>=20
  radiusext@ops.ietf.org<BR><B>Subject:</B> Bernard's =
notes<BR></FONT><BR></DIV>
  <DIV></DIV>Just a note to the WG to summarize where I think we are on =
various=20
  work items.&nbsp; The hope is that this note will disclose any =
disconnects=20
  which could lead to things falling through the cracks. <BR><BR>Issue =
List=20
  (recently updated): http://www.drizzle.com/~aboba/RADEXT/<BR><BR>1. =
Completed=20
  IESG Review: Revision Needed<BR><BR>My notes show two documents in =
this=20
  category:&nbsp; Design Guidelines and Status Server.&nbsp; In both =
cases, it=20
  appears to me that the editor (Alan DeKok) is holding the =
token.<BR><BR>Design=20
  Guidelines<BR><BR>This document currently has no open IESG DISCUSSes.=20
  <BR><BR>With respect to Design Guidelines, we have two issues in the =
Pending=20
  state:&nbsp; 325 and 327.&nbsp; Alan has updated the draft to -13, and =
has=20
  posted a request for review of the changes to address both =
issues.&nbsp; There=20
  is a discussion of Issue 327 in progress.&nbsp; In the absence of =
further=20
  discussion on Issue 325, we are going to assume that it has been =
resolved.=20
  <BR><BR>Next steps: WG participants are requested to review the Design =

  Guidelines document and post their thoughts to the=20
  =
list:<BR>http://tools.ietf.org/html/draft-ietf-radext-design<BR><BR>Statu=
s=20
  Server<BR><BR>This document currently has IESG DISCUSS comments open =
(see=20
  Issue #333), in addition to IETF last call comments (Issue # =
330).&nbsp;=20
  <BR><BR>Next steps:&nbsp; The editor need to address the open issues,=20
  preferably by posting a document revision.&nbsp; <BR><BR>2. AD =
Review:&nbsp;=20
  Revision Needed<BR><BR>My notes show one document in this =
category:&nbsp;=20
  RADIUS over TCP, with the editor (Alan DeKok) holding the token..=20
  <BR><BR>There are two open issues relating to the Dan's AD =
review:&nbsp;=20
  Issues 331 (technical) and 332 (editorial).&nbsp; <BR><BR>Next =
steps:&nbsp;=20
  The editor needs to address the open issues, preferably by posting a =
document=20
  revision. <BR><BR>3. Completed RADEXT WG Last Call: Pending PROTO=20
  Writeup<BR><BR>My notes show one document in this category:&nbsp; =
Tunnel Type=20
  Values, with Dave Nelson holding the token. <BR><BR>In the past, there =
had=20
  been some discussion about whether RFC 3575 intended to change the =
IANA=20
  allocation process for Tunnel-Type values to "expert review", even =
though it=20
  did not include RFC 2868 in the Updates: header.&nbsp;&nbsp; If so, =
could an=20
  errata if approved make this document unnecessary (given that an =
expert review=20
  has already been done)?&nbsp; <BR><BR>Next steps:&nbsp; Dave Nelson to =

  complete the PROTO writeup. <BR><BR>4. Completed RADEXT WG last call: =
Revision=20
  needed.<BR><BR>My notes show one document in this category:&nbsp; IPv6 =

  Access.&nbsp; <BR><BR>There is one issue outstanding from the RADEXT =
WG last=20
  call:&nbsp; Issue #335. <BR><BR>Next steps:&nbsp; The editor needs to =
address=20
  the open issues, preferably by posting a document revision. <BR><BR>5. =

  Completed RADEXT WG last call:&nbsp; PROTO writeup. <BR><BR>My notes =
show one=20
  document in this category:&nbsp; RADIUS over TLS. <BR><BR>There are no =

  outstanding issues from RADEXT WG last call. <BR><BR>Next steps:&nbsp; =
Bernard=20
  Aboba to complete PROTO writeup; RADEXT WG participants to read the =
document=20
  and post comments to the list.=20
<BR><BR><BR><BR><BR><BR><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAE51A.0435A9B3--

--
to unsubscribe send a message to radiusext-request@ops.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, 25 Apr 2010 23:17:36 +0000
Message-ID: <BLU137-W20CFFD1E4C3104581A412393050@phx.gbl>
Content-Type: multipart/alternative; boundary="_9fc0c086-7c07-4180-a53f-e4f9cbdd5486_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Bernard's notes
Date: Sun, 25 Apr 2010 16:17:05 -0700
MIME-Version: 1.0

--_9fc0c086-7c07-4180-a53f-e4f9cbdd5486_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Just a note to the WG to summarize where I think we are on various work ite=
ms.  The hope is that this note will disclose any disconnects which could l=
ead to things falling through the cracks.=20

Issue List (recently updated): http://www.drizzle.com/~aboba/RADEXT/

1. Completed IESG Review: Revision Needed

My notes show two documents in this category:  Design Guidelines and Status=
 Server.  In both cases=2C it appears to me that the editor (Alan DeKok) is=
 holding the token.

Design Guidelines

This document currently has no open IESG DISCUSSes.=20

With respect to Design Guidelines=2C we have two issues in the Pending stat=
e:  325 and 327.  Alan has updated the draft to -13=2C and has posted a req=
uest for review of the changes to address both issues.  There is a discussi=
on of Issue 327 in progress.  In the absence of further discussion on Issue=
 325=2C we are going to assume that it has been resolved.=20

Next steps: WG participants are requested to review the Design Guidelines d=
ocument and post their thoughts to the list:
http://tools.ietf.org/html/draft-ietf-radext-design

Status Server

This document currently has IESG DISCUSS comments open (see Issue #333)=2C =
in addition to IETF last call comments (Issue # 330). =20

Next steps:  The editor need to address the open issues=2C preferably by po=
sting a document revision. =20

2. AD Review:  Revision Needed

My notes show one document in this category:  RADIUS over TCP=2C with the e=
ditor (Alan DeKok) holding the token..=20

There are two open issues relating to the Dan's AD review:  Issues 331 (tec=
hnical) and 332 (editorial). =20

Next steps:  The editor needs to address the open issues=2C preferably by p=
osting a document revision.=20

3. Completed RADEXT WG Last Call: Pending PROTO Writeup

My notes show one document in this category:  Tunnel Type Values=2C with Da=
ve Nelson holding the token.=20

In the past=2C there had been some discussion about whether RFC 3575 intend=
ed to change the IANA allocation process for Tunnel-Type values to "expert =
review"=2C even though it did not include RFC 2868 in the Updates: header. =
  If so=2C could an errata if approved make this document unnecessary (give=
n that an expert review has already been done)? =20

Next steps:  Dave Nelson to complete the PROTO writeup.=20

4. Completed RADEXT WG last call: Revision needed.

My notes show one document in this category:  IPv6 Access. =20

There is one issue outstanding from the RADEXT WG last call:  Issue #335.=20

Next steps:  The editor needs to address the open issues=2C preferably by=20
posting a document revision.=20

5. Completed RADEXT WG last call:  PROTO writeup.=20

My notes show one document in this category:  RADIUS over TLS.=20

There are no outstanding issues from RADEXT WG last call.=20

Next steps:  Bernard Aboba to complete PROTO writeup=3B RADEXT WG participa=
nts to read the document and post comments to the list.=20






 		 	   		  =

--_9fc0c086-7c07-4180-a53f-e4f9cbdd5486_
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'>
Just a note to the WG to summarize where I think we are on various work ite=
ms.&nbsp=3B The hope is that this note will disclose any disconnects which =
could lead to things falling through the cracks. <br><br>Issue List (recent=
ly updated): http://www.drizzle.com/~aboba/RADEXT/<br><br>1. Completed IESG=
 Review: Revision Needed<br><br>My notes show two documents in this categor=
y:&nbsp=3B Design Guidelines and Status Server.&nbsp=3B In both cases=2C it=
 appears to me that the editor (Alan DeKok) is holding the token.<br><br>De=
sign Guidelines<br><br>This document currently has no open IESG DISCUSSes. =
<br><br>With respect to Design Guidelines=2C we have two issues in the Pend=
ing state:&nbsp=3B 325 and 327.&nbsp=3B Alan has updated the draft to -13=
=2C and has posted a request for review of the changes to address both issu=
es.&nbsp=3B There is a discussion of Issue 327 in progress.&nbsp=3B In the =
absence of further discussion on Issue 325=2C we are going to assume that i=
t has been resolved. <br><br>Next steps: WG participants are requested to r=
eview the Design Guidelines document and post their thoughts to the list:<b=
r>http://tools.ietf.org/html/draft-ietf-radext-design<br><br>Status Server<=
br><br>This document currently has IESG DISCUSS comments open (see Issue #3=
33)=2C in addition to IETF last call comments (Issue # 330).&nbsp=3B <br><b=
r>Next steps:&nbsp=3B The editor need to address the open issues=2C prefera=
bly by posting a document revision.&nbsp=3B <br><br>2. AD Review:&nbsp=3B R=
evision Needed<br><br>My notes show one document in this category:&nbsp=3B =
RADIUS over TCP=2C with the editor (Alan DeKok) holding the token.. <br><br=
>There are two open issues relating to the Dan's AD review:&nbsp=3B Issues =
331 (technical) and 332 (editorial).&nbsp=3B <br><br>Next steps:&nbsp=3B Th=
e editor needs to address the open issues=2C preferably by posting a docume=
nt revision. <br><br>3. Completed RADEXT WG Last Call: Pending PROTO Writeu=
p<br><br>My notes show one document in this category:&nbsp=3B Tunnel Type V=
alues=2C with Dave Nelson holding the token. <br><br>In the past=2C there h=
ad been some discussion about whether RFC 3575 intended to change the IANA =
allocation process for Tunnel-Type values to "expert review"=2C even though=
 it did not include RFC 2868 in the Updates: header.&nbsp=3B&nbsp=3B If so=
=2C could an errata if approved make this document unnecessary (given that =
an expert review has already been done)?&nbsp=3B <br><br>Next steps:&nbsp=
=3B Dave Nelson to complete the PROTO writeup. <br><br>4. Completed RADEXT =
WG last call: Revision needed.<br><br>My notes show one document in this ca=
tegory:&nbsp=3B IPv6 Access.&nbsp=3B <br><br>There is one issue outstanding=
 from the RADEXT WG last call:&nbsp=3B Issue #335. <br><br>Next steps:&nbsp=
=3B The editor needs to address the open issues=2C preferably by=20
posting a document revision. <br><br>5. Completed RADEXT WG last call:&nbsp=
=3B PROTO writeup. <br><br>My notes show one document in this category:&nbs=
p=3B RADIUS over TLS. <br><br>There are no outstanding issues from RADEXT W=
G last call. <br><br>Next steps:&nbsp=3B Bernard Aboba to complete PROTO wr=
iteup=3B RADEXT WG participants to read the document and post comments to t=
he list. <br><br><br><br><br><br><br> 		 	   		  </body>
</html>=

--_9fc0c086-7c07-4180-a53f-e4f9cbdd5486_--

--
to unsubscribe send a message to radiusext-request@ops.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, 25 Apr 2010 22:50:21 +0000
Message-ID: <BLU137-DS346EDD650AB6D0393D2AB93050@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Stefan Winter'" <mail@stefan-winter.de>
CC: <radiusext@ops.ietf.org>
Subject: RE: RADEXT WG Last Call on "TLS Encryption for RADIUS" (Experimental)
Date: Sun, 25 Apr 2010 15:49:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acrgfuefb9xGl/YsSY6SxYOksHnG9wESck5g
Content-Language: en-us

I am starting work on a PROTO writeup for this document, on the assumption
that "lack of response implies consent".  If any issues become apparent 
in the course of that review, I'll post them to the list. 

While that's in progress,  WG participants are encouraged to:

a. Read the document, and post any thoughts to the list (even if that is
only
"the document appears ready"); 
b. Continue to make progress on closing issues within dependency documents 
(e.g. RADIUS over TCP, Status-Server); 
c. Post updates on implementation progress; 

Thanks for your efforts on this document!

-----Original Message-----
From: Stefan Winter [mailto:mail@stefan-winter.de] 
Sent: Tuesday, April 20, 2010 4:45 AM
To: Bernard Aboba
Subject: Re: RADEXT WG Last Call on "TLS Encryption for RADIUS"
(Experimental)

Hi,

so...? Is the absence of comments enough to justify going on to IETF LC?
Would be much appreciated :-)

Stefan

Am 19.03.2010 20:59, schrieb Bernard Aboba:
> This is an announcement of RADEXT WG last call on "TLS Encryption for
> RADIUS", prior to sending the document to the IESG for publication as
> an Experimental RFC.
>
> The document is available for inspection here:
> http://tools.ietf.org/html/draft-ietf-radext-radsec
>
> The RADEXT WG last call will last until April 19, 2010.   If you have
> comments on the document, please send them to the RADEXT WG mailing
> list (radiusext@ops.ietf.org) in the format described on the RADEXT
> Issues list (http://www.drizzle.com/~aboba/RADEXT/ ). 



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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 22 Apr 2010 16:40:50 +0000
Message-ID: <4BD07BEC.6070808@deployingradius.com>
Date: Thu, 22 Apr 2010 18:40:12 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, radiusext@ops.ietf.org
Subject: Re: COMMENT: draft-ietf-radext-status-server
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Romascanu, Dan (Dan) wrote:
> I have not seen any response from you to the issues raised in the
> DISCUSS and COMMENT made by the different AD's. The IESG telechat is
> scheduled for today at 11:30AM ET. Are you on line and preparing answers
> to the issues raised?

  Vacation... just responded to most, hope it's not too late.

  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, 22 Apr 2010 08:04:54 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAE1F2.5316F534"
Subject: RE: COMMENT: draft-ietf-radext-status-server
Date: Thu, 22 Apr 2010 10:03:41 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402103ED0@307622ANEX5.global.avaya.com>
Thread-Topic: COMMENT: draft-ietf-radext-status-server
Thread-Index: AcrhutvV56TC0t3wRcCDnGH97WYhGAAN0MAA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Alan DeKok" <aland@deployingradius.com>
Cc: "Bernard Aboba" <bernard_aboba@hotmail.com>, <radiusext@ops.ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAE1F2.5316F534
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Alan,
=20
I have not seen any response from you to the issues raised in the
DISCUSS and COMMENT made by the different AD's. The IESG telechat is
scheduled for today at 11:30AM ET. Are you on line and preparing answers
to the issues raised?=20
=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: Thursday, April 22, 2010 4:25 AM
	To: radiusext@ops.ietf.org
	Subject: COMMENT: draft-ietf-radext-status-server
=09
=09

	> From: housley@vigilsec.com
	> To: iesg@ietf.org
	> CC: Francis.Dupont@fdupont.fr; radext-chairs@tools.ietf.org;
draft-ietf-radext-status-server@tools.ietf.org
	> Date: Wed, 21 Apr 2010 18:22:24 -0700
	> Subject: COMMENT: draft-ietf-radext-status-server=20
	>=20
	> Comment:
	>=20
	> Please consider the comments from the Gen-ART Review by
Francis Dupont:
	>=20
	> - Abstract page 2: there is an explicit reference to a RFC,
this is in
	> general forbidden but IMHO we are here in the allowed
exception case.
	>=20
	> - 2.1.1 page 8: a servers policy -> a server policy
	>=20
	> - 3 page 10 (twice): etc. -> etc., ???
	>=20
	> - 4.2 page 13: adminstrators -> administrators
	>=20
	> - 4.2 page 15 (twice): e.g. -> e.g.,
	>=20
	> - 4.3 page 16: modelled -> modeled
	>=20
	> - 4.3 page 16: usually the hysteresis against flapping tries
to keep
	> the connection (i.e., failover after 3 missed responses), here
it is
	> the opposite. IMHO it is very aggressive but it is how RFC
3539 works
	> so I have no concern about it.
	>=20
	> - 4.5 page 16: Proxyhas -> Proxy has
	>=20
	> - 4.5 page 17: cannot, -> cannot
	>=20
	> - 4.5 page 18: i.e. -> i.e.,
	>=20
	> - 5 page 19: EAP-MEssage -> EAP-Message
	>=20
	> - 8 page 23: synthesise -> synthesize
	>=20
	> - 8 page 23: in "the suggestion of [RFC5080] Section 2.2.2,
which suggests"
	> suggests -> proposes
	>=20
	> - 8 page 23: configurably is not in my dict?
	>=20
	> - 9.2 page 23: IMHO the RFC2119 reference should be moved to
normative
	> references section (perhaps others too?)
	>=20
	> - Authors' Addresses -> Author's Address
	>=20
=09
=09


------_=_NextPart_001_01CAE1F2.5316F534
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

<META content=3D"MSHTML 6.00.2900.5945" name=3DGENERATOR></HEAD>
<BODY class=3Dhmmessage dir=3Dltr>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010>Alan,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN =
class=3D945140208-22042010>I have not=20
seen any response from you to the issues raised in the DISCUSS and =
COMMENT made=20
by the different AD's. The IESG telechat is scheduled for today at =
11:30AM ET.=20
Are you on line and preparing answers to the issues raised? =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN =
class=3D945140208-22042010>Thanks and=20
Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010>Dan</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D945140208-22042010></SPAN></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma><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> Thursday, April 22, 2010 4:25 AM<BR><B>To:</B>=20
  radiusext@ops.ietf.org<BR><B>Subject:</B> COMMENT:=20
  draft-ietf-radext-status-server<BR></FONT><BR></DIV>
  <DIV></DIV><BR>&gt; From: housley@vigilsec.com<BR>&gt; To:=20
  iesg@ietf.org<BR>&gt; CC: Francis.Dupont@fdupont.fr;=20
  radext-chairs@tools.ietf.org;=20
  draft-ietf-radext-status-server@tools.ietf.org<BR>&gt; Date: Wed, 21 =
Apr 2010=20
  18:22:24 -0700<BR>&gt; Subject: COMMENT: =
draft-ietf-radext-status-server=20
  <BR>&gt; <BR>&gt; Comment:<BR>&gt; <BR>&gt; Please consider the =
comments from=20
  the Gen-ART Review by Francis Dupont:<BR>&gt; <BR>&gt; - Abstract page =
2:=20
  there is an explicit reference to a RFC, this is in<BR>&gt; general =
forbidden=20
  but IMHO we are here in the allowed exception case.<BR>&gt; <BR>&gt; - =
2.1.1=20
  page 8: a servers policy -&gt; a server policy<BR>&gt; <BR>&gt; - 3 =
page 10=20
  (twice): etc. -&gt; etc., ???<BR>&gt; <BR>&gt; - 4.2 page 13: =
adminstrators=20
  -&gt; administrators<BR>&gt; <BR>&gt; - 4.2 page 15 (twice): e.g. =
-&gt;=20
  e.g.,<BR>&gt; <BR>&gt; - 4.3 page 16: modelled -&gt; modeled<BR>&gt; =
<BR>&gt;=20
  - 4.3 page 16: usually the hysteresis against flapping tries to =
keep<BR>&gt;=20
  the connection (i.e., failover after 3 missed responses), here it =
is<BR>&gt;=20
  the opposite. IMHO it is very aggressive but it is how RFC 3539 =
works<BR>&gt;=20
  so I have no concern about it.<BR>&gt; <BR>&gt; - 4.5 page 16: =
Proxyhas -&gt;=20
  Proxy has<BR>&gt; <BR>&gt; - 4.5 page 17: cannot, -&gt; cannot<BR>&gt; =

  <BR>&gt; - 4.5 page 18: i.e. -&gt; i.e.,<BR>&gt; <BR>&gt; - 5 page 19: =

  EAP-MEssage -&gt; EAP-Message<BR>&gt; <BR>&gt; - 8 page 23: synthesise =
-&gt;=20
  synthesize<BR>&gt; <BR>&gt; - 8 page 23: in "the suggestion of =
[RFC5080]=20
  Section 2.2.2, which suggests"<BR>&gt; suggests -&gt; proposes<BR>&gt; =

  <BR>&gt; - 8 page 23: configurably is not in my dict?<BR>&gt; <BR>&gt; =
- 9.2=20
  page 23: IMHO the RFC2119 reference should be moved to =
normative<BR>&gt;=20
  references section (perhaps others too?)<BR>&gt; <BR>&gt; - Authors' =
Addresses=20
  -&gt; Author's Address<BR>&gt; <BR><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAE1F2.5316F534--

--
to unsubscribe send a message to radiusext-request@ops.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, 22 Apr 2010 01:26:09 +0000
Message-ID: <BLU137-W66E08672FD489DD69AF5A93080@phx.gbl>
Content-Type: multipart/alternative; boundary="_23987067-6fc3-48d5-8453-1148c1a5d6cc_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: COMMENT: draft-ietf-radext-status-server
Date: Wed, 21 Apr 2010 18:25:24 -0700
MIME-Version: 1.0

--_23987067-6fc3-48d5-8453-1148c1a5d6cc_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



> From: housley@vigilsec.com
> To: iesg@ietf.org
> CC: Francis.Dupont@fdupont.fr=3B radext-chairs@tools.ietf.org=3B draft-ie=
tf-radext-status-server@tools.ietf.org
> Date: Wed=2C 21 Apr 2010 18:22:24 -0700
> Subject: COMMENT: draft-ietf-radext-status-server=20
>=20
> Comment:
>=20
> Please consider the comments from the Gen-ART Review by Francis Dupont:
>=20
> - Abstract page 2: there is an explicit reference to a RFC=2C this is in
> general forbidden but IMHO we are here in the allowed exception case.
>=20
> - 2.1.1 page 8: a servers policy -> a server policy
>=20
> - 3 page 10 (twice): etc. -> etc.=2C ???
>=20
> - 4.2 page 13: adminstrators -> administrators
>=20
> - 4.2 page 15 (twice): e.g. -> e.g.=2C
>=20
> - 4.3 page 16: modelled -> modeled
>=20
> - 4.3 page 16: usually the hysteresis against flapping tries to keep
> the connection (i.e.=2C failover after 3 missed responses)=2C here it is
> the opposite. IMHO it is very aggressive but it is how RFC 3539 works
> so I have no concern about it.
>=20
> - 4.5 page 16: Proxyhas -> Proxy has
>=20
> - 4.5 page 17: cannot=2C -> cannot
>=20
> - 4.5 page 18: i.e. -> i.e.=2C
>=20
> - 5 page 19: EAP-MEssage -> EAP-Message
>=20
> - 8 page 23: synthesise -> synthesize
>=20
> - 8 page 23: in "the suggestion of [RFC5080] Section 2.2.2=2C which sugge=
sts"
> suggests -> proposes
>=20
> - 8 page 23: configurably is not in my dict?
>=20
> - 9.2 page 23: IMHO the RFC2119 reference should be moved to normative
> references section (perhaps others too?)
>=20
> - Authors' Addresses -> Author's Address
>=20

 		 	   		  =

--_23987067-6fc3-48d5-8453-1148c1a5d6cc_
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'>
<BR>&gt=3B From: housley@vigilsec.com<BR>&gt=3B To: iesg@ietf.org<BR>&gt=3B=
 CC: Francis.Dupont@fdupont.fr=3B radext-chairs@tools.ietf.org=3B draft-iet=
f-radext-status-server@tools.ietf.org<BR>&gt=3B Date: Wed=2C 21 Apr 2010 18=
:22:24 -0700<BR>&gt=3B Subject: COMMENT: draft-ietf-radext-status-server <B=
R>&gt=3B <BR>&gt=3B Comment:<BR>&gt=3B <BR>&gt=3B Please consider the comme=
nts from the Gen-ART Review by Francis Dupont:<BR>&gt=3B <BR>&gt=3B - Abstr=
act page 2: there is an explicit reference to a RFC=2C this is in<BR>&gt=3B=
 general forbidden but IMHO we are here in the allowed exception case.<BR>&=
gt=3B <BR>&gt=3B - 2.1.1 page 8: a servers policy -&gt=3B a server policy<B=
R>&gt=3B <BR>&gt=3B - 3 page 10 (twice): etc. -&gt=3B etc.=2C ???<BR>&gt=3B=
 <BR>&gt=3B - 4.2 page 13: adminstrators -&gt=3B administrators<BR>&gt=3B <=
BR>&gt=3B - 4.2 page 15 (twice): e.g. -&gt=3B e.g.=2C<BR>&gt=3B <BR>&gt=3B =
- 4.3 page 16: modelled -&gt=3B modeled<BR>&gt=3B <BR>&gt=3B - 4.3 page 16:=
 usually the hysteresis against flapping tries to keep<BR>&gt=3B the connec=
tion (i.e.=2C failover after 3 missed responses)=2C here it is<BR>&gt=3B th=
e opposite. IMHO it is very aggressive but it is how RFC 3539 works<BR>&gt=
=3B so I have no concern about it.<BR>&gt=3B <BR>&gt=3B - 4.5 page 16: Prox=
yhas -&gt=3B Proxy has<BR>&gt=3B <BR>&gt=3B - 4.5 page 17: cannot=2C -&gt=
=3B cannot<BR>&gt=3B <BR>&gt=3B - 4.5 page 18: i.e. -&gt=3B i.e.=2C<BR>&gt=
=3B <BR>&gt=3B - 5 page 19: EAP-MEssage -&gt=3B EAP-Message<BR>&gt=3B <BR>&=
gt=3B - 8 page 23: synthesise -&gt=3B synthesize<BR>&gt=3B <BR>&gt=3B - 8 p=
age 23: in "the suggestion of [RFC5080] Section 2.2.2=2C which suggests"<BR=
>&gt=3B suggests -&gt=3B proposes<BR>&gt=3B <BR>&gt=3B - 8 page 23: configu=
rably is not in my dict?<BR>&gt=3B <BR>&gt=3B - 9.2 page 23: IMHO the RFC21=
19 reference should be moved to normative<BR>&gt=3B references section (per=
haps others too?)<BR>&gt=3B <BR>&gt=3B - Authors' Addresses -&gt=3B Author'=
s Address<BR>&gt=3B <BR><BR> 		 	   		  </body>
</html>=

--_23987067-6fc3-48d5-8453-1148c1a5d6cc_--

--
to unsubscribe send a message to radiusext-request@ops.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, 21 Apr 2010 22:20:48 +0000
Message-ID: <BLU137-W7892528D73B56E7638DD493090@phx.gbl>
Content-Type: multipart/alternative; boundary="_b8c58574-3e51-4c71-a9fe-026822cca349_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: COMMENT: draft-ietf-radext-status-server
Date: Wed, 21 Apr 2010 15:19:54 -0700
MIME-Version: 1.0

--_b8c58574-3e51-4c71-a9fe-026822cca349_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



> From: turners@ieca.com
> To: iesg@ietf.org
> CC: radext-chairs@tools.ietf.org=3B draft-ietf-radext-status-server@tools=
.ietf.org
> Date: Wed=2C 21 Apr 2010 14:43:40 -0700
> Subject: COMMENT: draft-ietf-radext-status-server=20
>=20
> Comment:
> I support Peter's discuss. =20
>=20
> Additionally=2C I noted the same thing Peter did wrt to random numbers.
>=20
> Section 3: In the Request Authenticator description the two paragraphs re=
peat that Request Authentication SHOULD be unpredictable and then says why.=
 Maybe the second paragraph should be tweaked:
>=20
>  The Request Authenticator value in a Status-Server packet
>  SHOULD also be unpredictable **because** an attacker **could**
>  trick a server
>  into responding to a predicted future request=2C and then use the
>  response to masquerade as that server to a future Status-Server
>  request from a client.
>=20
 		 	   		  =

--_b8c58574-3e51-4c71-a9fe-026822cca349_
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'>
<br>&gt=3B From: turners@ieca.com<br>&gt=3B To: iesg@ietf.org<br>&gt=3B CC:=
 radext-chairs@tools.ietf.org=3B draft-ietf-radext-status-server@tools.ietf=
.org<br>&gt=3B Date: Wed=2C 21 Apr 2010 14:43:40 -0700<br>&gt=3B Subject: C=
OMMENT: draft-ietf-radext-status-server <br>&gt=3B <br>&gt=3B Comment:<br>&=
gt=3B I support Peter's discuss.  <br>&gt=3B <br>&gt=3B Additionally=2C I n=
oted the same thing Peter did wrt to random numbers.<br>&gt=3B <br>&gt=3B S=
ection 3: In the Request Authenticator description the two paragraphs repea=
t that Request Authentication SHOULD be unpredictable and then says why. Ma=
ybe the second paragraph should be tweaked:<br>&gt=3B <br>&gt=3B  The Reque=
st Authenticator value in a Status-Server packet<br>&gt=3B  SHOULD also be =
unpredictable **because** an attacker **could**<br>&gt=3B  trick a server<b=
r>&gt=3B  into responding to a predicted future request=2C and then use the=
<br>&gt=3B  response to masquerade as that server to a future Status-Server=
<br>&gt=3B  request from a client.<br>&gt=3B <br> 		 	   		  </body>
</html>=

--_b8c58574-3e51-4c71-a9fe-026822cca349_--

--
to unsubscribe send a message to radiusext-request@ops.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, 20 Apr 2010 21:02:08 +0000
Message-ID: <BLU137-DS1074803E73A527CFB4BF31930A0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: DISCUSS and COMMENT: draft-ietf-radext-status-server 
Date: Tue, 20 Apr 2010 14:00:54 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQH+QAViIud9GCSFTz6M9KPhOW92qpHFGQqQ
Content-Language: en-us

-----Original Message-----
From: Peter Saint-Andre [mailto:stpeter@stpeter.im]=20
Sent: Tuesday, April 20, 2010 11:31 AM
To: iesg@ietf.org
Cc: aland@freeradius.org; radext-chairs@tools.ietf.org; =
draft-ietf-radext-status-server@tools.ietf.org
Subject: DISCUSS and COMMENT: draft-ietf-radext-status-server=20

Discuss:
Is the use of MD5 in generating the Response Authenticator subject to =
collision attacks? If not, it would be helpful to describe why not, and =
provide a reference to RFC 4270. If so, then the security considerations =
need to be updated.

Comment:
Given that the Request Authenticator should be unpredictable and unique, =
a reference to RFC 4086 would be appropriate.

Please add a reference to RFC 1321 for the definition of MD5.



--
to unsubscribe send a message to radiusext-request@ops.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, 19 Apr 2010 15:58:30 +0000
Message-ID: <BLU137-W30DADD024EF4A551174538930B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_39957140-d247-490a-96de-5f1c03b449f8_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: DISCUSS and COMMENT: draft-ietf-radext-status-server
Date: Mon, 19 Apr 2010 08:57:58 -0700
MIME-Version: 1.0

--_39957140-d247-490a-96de-5f1c03b449f8_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



> From: lars.eggert@nokia.com
> To: iesg@ietf.org
> CC: radext-chairs@tools.ietf.org=3B draft-ietf-radext-status-server@tools=
.ietf.org
> Date: Mon=2C 19 Apr 2010 06:58:54 -0700
> Subject: DISCUSS and COMMENT: draft-ietf-radext-status-server=20
>=20
> Discuss:
>=20
> Section 4.1.=2C paragraph 2:
> >    The client SHOULD also have a configurable global timer (Tw) that is
> >    used when sending periodic Status-Server queries during server fail-
> >    over.  The default value SHOULD be 30 seconds=2C and the value MUST =
NOT
> >    be permitted to be set below 6 seconds.  If a response has not been
> >    received within the timeout period=2C the Status-Server packet is
> >    deemed to have received no corresponding Response packet=2C and MUST=
 be
> >    discarded.
>=20
>   DISCUSS: I would like to discuss two issues with this design. First=2C
>   since it is only RECOMMENDED to implement Tw and not REQUIRED=2C client=
s
>   need not do so. How do clients without Tw decide that a server has not
>   responded?
>=20
>   Second=2C there is no discussion on what rate clients should
>   be using when *issuing* Status-Server queries. The current text allows
>   a client to send Status-Server queries to the server at high rates=2C
>   and does not require the client to reduce its sending rate when it
>   receives no responses. In other words=2C there currently isn't any sort
>   of congestion control. Has this been discussed by the working group?
>   It seems like all the pieces are already there to implement a simple
>   congestion control scheme: have clients issue at most one request per
>   Tw (already implied by Section 4.3 text but not clearly stated
>   anywhere)=2C double Tw up to some conservative maximum when the server
>   does not respond=2C restore the initial Tw when it does (Section 4.3
>   again has some text that goes into that direction).
>=20
> Comment:
>=20
> Section 1812.=2C paragraph 4:
>=20
> >    The server MAY prioritize the handling of Status-Server packets over
> >    the handling of other requests=2C subject to the rate limiting
> >    described above.
>=20
>   Without congestion control=2C implementing this MAY guarantees that the
>   minimum amount of useful (=3D non-Status-Server) work will be done.
>=20
>=20
> Section 4.3.=2C paragraph 3:
> >    If no response is received to Status-Server packets=2C the RADIUS
> >    client can initiate failover to another proxy.  By continuing to sen=
d
> >    Status-Server packets to the original proxy at an interval of Tw=2C =
the
> >    RADIUS client can determine when the original proxy becomes
> >    responsive again.
>=20
>   This uses Status-Server messages as an overload detection mechanism.
>   They need to be sent in a way that will back off the rate
>   under overload=2C because otherwise the scheme can turn into an
>   overload *generation* mechanism.
>=20
>=20
> Section 4.5.=2C paragraph 17:
> >    It is RECOMMENDED=2C therefore=2C that implementations desiring the =
most
> >    benefit from Status-Server also implement server failover.  The
> >    combination of these two practices will maximize network reliability
> >    and stability.
>=20
>   If Status-Server messages are being sent in a way that is congestion
>   controlled (i.e.=2C the rate is reduced under overload).
>=20
 		 	   		  =

--_39957140-d247-490a-96de-5f1c03b449f8_
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'>
<br>&gt=3B From: lars.eggert@nokia.com<br>&gt=3B To: iesg@ietf.org<br>&gt=
=3B CC: radext-chairs@tools.ietf.org=3B draft-ietf-radext-status-server@too=
ls.ietf.org<br>&gt=3B Date: Mon=2C 19 Apr 2010 06:58:54 -0700<br>&gt=3B Sub=
ject: DISCUSS and COMMENT: draft-ietf-radext-status-server <br>&gt=3B <br>&=
gt=3B Discuss:<br>&gt=3B <br>&gt=3B Section 4.1.=2C paragraph 2:<br>&gt=3B =
&gt=3B    The client SHOULD also have a configurable global timer (Tw) that=
 is<br>&gt=3B &gt=3B    used when sending periodic Status-Server queries du=
ring server fail-<br>&gt=3B &gt=3B    over.  The default value SHOULD be 30=
 seconds=2C and the value MUST NOT<br>&gt=3B &gt=3B    be permitted to be s=
et below 6 seconds.  If a response has not been<br>&gt=3B &gt=3B    receive=
d within the timeout period=2C the Status-Server packet is<br>&gt=3B &gt=3B=
    deemed to have received no corresponding Response packet=2C and MUST be=
<br>&gt=3B &gt=3B    discarded.<br>&gt=3B <br>&gt=3B   DISCUSS: I would lik=
e to discuss two issues with this design. First=2C<br>&gt=3B   since it is =
only RECOMMENDED to implement Tw and not REQUIRED=2C clients<br>&gt=3B   ne=
ed not do so. How do clients without Tw decide that a server has not<br>&gt=
=3B   responded?<br>&gt=3B <br>&gt=3B   Second=2C there is no discussion on=
 what rate clients should<br>&gt=3B   be using when *issuing* Status-Server=
 queries. The current text allows<br>&gt=3B   a client to send Status-Serve=
r queries to the server at high rates=2C<br>&gt=3B   and does not require t=
he client to reduce its sending rate when it<br>&gt=3B   receives no respon=
ses. In other words=2C there currently isn't any sort<br>&gt=3B   of conges=
tion control. Has this been discussed by the working group?<br>&gt=3B   It =
seems like all the pieces are already there to implement a simple<br>&gt=3B=
   congestion control scheme: have clients issue at most one request per<br=
>&gt=3B   Tw (already implied by Section 4.3 text but not clearly stated<br=
>&gt=3B   anywhere)=2C double Tw up to some conservative maximum when the s=
erver<br>&gt=3B   does not respond=2C restore the initial Tw when it does (=
Section 4.3<br>&gt=3B   again has some text that goes into that direction).=
<br>&gt=3B <br>&gt=3B Comment:<br>&gt=3B <br>&gt=3B Section 1812.=2C paragr=
aph 4:<br>&gt=3B <br>&gt=3B &gt=3B    The server MAY prioritize the handlin=
g of Status-Server packets over<br>&gt=3B &gt=3B    the handling of other r=
equests=2C subject to the rate limiting<br>&gt=3B &gt=3B    described above=
.<br>&gt=3B <br>&gt=3B   Without congestion control=2C implementing this MA=
Y guarantees that the<br>&gt=3B   minimum amount of useful (=3D non-Status-=
Server) work will be done.<br>&gt=3B <br>&gt=3B <br>&gt=3B Section 4.3.=2C =
paragraph 3:<br>&gt=3B &gt=3B    If no response is received to Status-Serve=
r packets=2C the RADIUS<br>&gt=3B &gt=3B    client can initiate failover to=
 another proxy.  By continuing to send<br>&gt=3B &gt=3B    Status-Server pa=
ckets to the original proxy at an interval of Tw=2C the<br>&gt=3B &gt=3B   =
 RADIUS client can determine when the original proxy becomes<br>&gt=3B &gt=
=3B    responsive again.<br>&gt=3B <br>&gt=3B   This uses Status-Server mes=
sages as an overload detection mechanism.<br>&gt=3B   They need to be sent =
in a way that will back off the rate<br>&gt=3B   under overload=2C because =
otherwise the scheme can turn into an<br>&gt=3B   overload *generation* mec=
hanism.<br>&gt=3B <br>&gt=3B <br>&gt=3B Section 4.5.=2C paragraph 17:<br>&g=
t=3B &gt=3B    It is RECOMMENDED=2C therefore=2C that implementations desir=
ing the most<br>&gt=3B &gt=3B    benefit from Status-Server also implement =
server failover.  The<br>&gt=3B &gt=3B    combination of these two practice=
s will maximize network reliability<br>&gt=3B &gt=3B    and stability.<br>&=
gt=3B <br>&gt=3B   If Status-Server messages are being sent in a way that i=
s congestion<br>&gt=3B   controlled (i.e.=2C the rate is reduced under over=
load).<br>&gt=3B <br> 		 	   		  </body>
</html>=

--_39957140-d247-490a-96de-5f1c03b449f8_--

--
to unsubscribe send a message to radiusext-request@ops.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, 19 Apr 2010 15:58:22 +0000
Message-ID: <BLU137-W64CCF24BD8E6473D2F0AE930B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_96f5e7e6-23ed-451e-9199-83ca09bd3329_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: nits: draft-ietf-radext-status-server
Date: Mon, 19 Apr 2010 08:57:27 -0700
MIME-Version: 1.0

--_96f5e7e6-23ed-451e-9199-83ca09bd3329_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



> From: lars.eggert@nokia.com
> Date: Mon=2C 19 Apr 2010 17:07:54 +0300
> To: draft-ietf-radext-status-server@tools.ietf.org=3B radext-chairs@tools=
.ietf.org=3B radext-ads@tools.ietf.org
> Subject: nits: draft-ietf-radext-status-server=20
>=20
>   Note: Most comments marked as "nits" below have been automatically
>  flagged by review scripts - there may be some false positives in there.
>=20
>=20
>=20
> Section 4.1.=2C paragraph 9:
> >    to send Request packets.  In that case=2C the Identifer field MUST b=
e
>=20
>   Nit: s/Identifer/Identifier/
>=20
>=20
> Section 4.2.=2C paragraph 1:
> >    it is enabled.  Servers SHOULD also permit adminstrators to enable o=
r
>=20
>   Nit: s/adminstrators/administrators/
>=20
>=20
>=20
> Section 4.3.=2C paragraph 4:
> >    accounting ports.  The client MUST treat each destination (ip=2C por=
t)
>=20
>   Nit: s/(ip=2C/(IP=2C/
>=20
>=20
> Section 4.5.=2C paragraph 4:
> >    Each RADIUS Proxyhas relationships with RADIUS Servers for both Real=
m
>=20
>   Nit: s/Proxyhas/Proxy has/
>=20
>=20
> Section 0=2C paragraph 0:
> >    0        0        0            70   EAP-MEssage
>=20
>   Nit: s/EAP-MEssage/EAP-Message/
>=20
>=20
 		 	   		  =

--_96f5e7e6-23ed-451e-9199-83ca09bd3329_
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'>
<br>&gt=3B From: lars.eggert@nokia.com<br>&gt=3B Date: Mon=2C 19 Apr 2010 1=
7:07:54 +0300<br>&gt=3B To: draft-ietf-radext-status-server@tools.ietf.org=
=3B radext-chairs@tools.ietf.org=3B radext-ads@tools.ietf.org<br>&gt=3B Sub=
ject: nits: draft-ietf-radext-status-server <br>&gt=3B <br>&gt=3B   Note: M=
ost comments marked as "nits" below have been automatically<br>&gt=3B  flag=
ged by review scripts - there may be some false positives in there.<br>&gt=
=3B <br>&gt=3B <br>&gt=3B <br>&gt=3B Section 4.1.=2C paragraph 9:<br>&gt=3B=
 &gt=3B    to send Request packets.  In that case=2C the Identifer field MU=
ST be<br>&gt=3B <br>&gt=3B   Nit: s/Identifer/Identifier/<br>&gt=3B <br>&gt=
=3B <br>&gt=3B Section 4.2.=2C paragraph 1:<br>&gt=3B &gt=3B    it is enabl=
ed.  Servers SHOULD also permit adminstrators to enable or<br>&gt=3B <br>&g=
t=3B   Nit: s/adminstrators/administrators/<br>&gt=3B <br>&gt=3B <br>&gt=3B=
 <br>&gt=3B Section 4.3.=2C paragraph 4:<br>&gt=3B &gt=3B    accounting por=
ts.  The client MUST treat each destination (ip=2C port)<br>&gt=3B <br>&gt=
=3B   Nit: s/(ip=2C/(IP=2C/<br>&gt=3B <br>&gt=3B <br>&gt=3B Section 4.5.=2C=
 paragraph 4:<br>&gt=3B &gt=3B    Each RADIUS Proxyhas relationships with R=
ADIUS Servers for both Realm<br>&gt=3B <br>&gt=3B   Nit: s/Proxyhas/Proxy h=
as/<br>&gt=3B <br>&gt=3B <br>&gt=3B Section 0=2C paragraph 0:<br>&gt=3B &gt=
=3B    0        0        0            70   EAP-MEssage<br>&gt=3B <br>&gt=3B=
   Nit: s/EAP-MEssage/EAP-Message/<br>&gt=3B <br>&gt=3B <br> 		 	   		  </b=
ody>
</html>=

--_96f5e7e6-23ed-451e-9199-83ca09bd3329_--

--
to unsubscribe send a message to radiusext-request@ops.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, 16 Apr 2010 14:36:42 +0000
Message-ID: <4BC875D5.1060802@deployingradius.com>
Date: Fri, 16 Apr 2010 16:36:05 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: I-D Action:draft-ietf-radext-design-13.txt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> Glancing at -13, there appear to be some inconsistencies within the text:
> 
> Section 1.3.1
...
> [BA] This text is similar to text in Section 3.3.3, which leads me to
> believe that there was an editing problem.

  The intent was to start off defining situations where SDOs did *not*
require review, and to later discuss situations where they did need review.

> My suggestion is that the text in 3.3.3 be moved to Section 1.3.1.

  Hmm... it's substantially similar to 3.3.2, but directed towards SDOs
rather than vendors.  I'd prefer to leave it where it is, but there are
arguments to be made both ways.

> Nevertheless, following the guidelines outlined within this document
> has many advantages. It is therefore RECOMMENDED that SDOs follow
> the guidelines outlined here, which are intended to enable maximum
> interoperability with minimal changes to existing systems.
> 
> [BA] The last paragraph does not appear to be consistent with Section 1.3,
> so I'd
> recommend that it be deleted.

  I'm not sure what isn't consistent, but OK.

> 3.3.2. Vendor Allocations
> 
> Nevertheless, following the guidelines outlined within this document
> has many advantages. It is therefore RECOMMENDED that vendors follow
> the guidelines outlined here, which are intended to enable maximum
> interoperability with minimal changes to existing systems. If these
> guidelines are not followed, the result will be increased complexity
> with little or no benefit.
> 
> [BA] The resolution to Issue 327 recommended the following alternative text:

  OK.  I was trying to avoid repeating the discussion on dictionaries
and code changes...

> 3.3.4. Publication of specifications
...
> [BA] The resolution to Issue 327 recommended the following alternative text:

  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: Thu, 15 Apr 2010 16:07:19 +0000
Message-ID: <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl>
Content-Type: multipart/alternative; boundary="_1de28bcc-3e9d-4f65-87b0-855562c143b3_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Alan DeKok <aland@deployingradius.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RE: I-D Action:draft-ietf-radext-design-13.txt
Date: Thu, 15 Apr 2010 09:06:26 -0700
MIME-Version: 1.0

--_1de28bcc-3e9d-4f65-87b0-855562c143b3_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Glancing at -13=2C there appear to be some inconsistencies within the text:

Section 1.3.1

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.

It is RECOMMENDED that SDOs follow the guidelines articulated in this
document. 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 new attributes defined in those
specifications are VSAs. See Section 3=2C below=2C for additional
discussion of this topic.

It is RECOMMENDED that SDOs and vendors seek review of RADIUS
attribute specifications from the IETF. However=2C specifications do
not require IETF review when they satisfy all of the following
criteria:

* are SDO specific=3B

* reference attributes from pre-existing IETF or SDO
specifications=3B

* define new attributes only in the VSA space=3B

* use only the "basic data types" (see below) for all VSAs=3B

* follow the guidelines given in this document.

[BA] This text is similar to text in Section 3.3.3=2C which leads me to
believe that there was an editing problem.
My suggestion is that the text in 3.3.3 be moved to Section 1.3.1.

3.3.3. SDO Allocations

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. Is is therefore RECOMMENDED
that SDO RADIUS Attribute specifications 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:

* attributes relying on data types not defined within RADIUS

* attributes intended primarily for use within an SDO

* attributes intended primarily for use within a group of SDOs.

Any 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].

The recommendation for SDOs to allocate attributes from a vendor
space rather than via the IETF process is a recognition that SDOs
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. The SDO can then allocate
attributes within the VSA space defined by that Vendor-Id=2C at their
sole discretion. Similarly=2C the use of data types (complex or
otherwise) within that VSA space is solely under the discretion of
the SDO.

Nevertheless=2C following the guidelines outlined within this document
has many advantages. It is therefore RECOMMENDED that SDOs follow
the guidelines outlined here=2C which are intended to enable maximum
interoperability with minimal changes to existing systems.

[BA] The last paragraph does not appear to be consistent with Section 1.3=
=2C
so I'd
recommend that it be deleted.

3.3.2. Vendor Allocations

Nevertheless=2C following the guidelines outlined within this document
has many advantages. It is therefore RECOMMENDED that vendors follow
the guidelines outlined here=2C which are intended to enable maximum
interoperability with minimal changes to existing systems. If these
guidelines are not followed=2C the result will be increased complexity
with little or no benefit.

[BA] The resolution to Issue 327 recommended the following alternative text=
:

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
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."

3.3.4. Publication of specifications

In order to enable IETF review of SDO specifications=2C it is
RECOMMENDED that:

* SDOs make their RADIUS attribute specifications publicly
available=3B

* SDOs request review of RADIUS attribute specifications by
sending email to the AAA Doctors [DOCTORS] or equivalent mailing
list=3B

* IETF and SDO RADIUS attribute specifications are reviewed
according to the guidelines proposed in this document=3B

* 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.

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.

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.

SDOs are encouraged to seek early review of their specifications by
the IETF. It should be understood that reviews are a voluntary-based
service offered on best-effort basis.

Where the RADIUS 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.

Similarly=2C vendors are encouraged to make their specifications
publicly available=2C for maximum interoperability. However=2C it is not
necessary for them to request publication of their VSA specifications
as Informational RFCs by the IETF.

All other specifications=2C including new authentication=2C
authorization=2C and/or security mechanisms SHOULD follow the
allocation process defined in [RFC3575].

[BA] The resolution to Issue 327 recommended the following alternative text=
:

SDOs or vendors desiring review of their RADIUS specifications
by the IETF are encouraged to seek review as early as possible=2C
so as to avoid potential delays. Since reviews are handled by volunteers=2C
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
an Informational RFC=2C as with [RFC4679].

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.

The review process requires neither allocation of attributes
within the IETF standard attribute space nor publication of an
IETF RFC. Requiring SDOs or vendors to rehost VSAs into the IETF standards
attribute space solely for the purpose of obtaining review
would put pressure on the standards space=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."

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] =
On
> Behalf Of Alan DeKok
> Sent: Wednesday=2C April 14=2C 2010 5:55 AM
> To: radiusext@ops.ietf.org
> Subject: Re: I-D Action:draft-ietf-radext-design-13.txt
>=20
> Internet-Drafts@ietf.org wrote:
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the RADIUS EXTensions Working Group of the
> IETF.
> >=20
> >=20
> > 	Title           : RADIUS Design Guidelines
> > 	Author(s)       : G. Weber=2C A. DeKok
> > 	Filename        : draft-ietf-radext-design-13.txt
> > 	Pages           : 40
> > 	Date            : 2010-04-14
>=20
>   See also the 'diff' available at:
>=20
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-radext-design-13.txt
>=20
>   This revision incorporates suggestions from all open issues=2C includin=
g
> #327.
>=20
>   Please provide feedback.
>=20
>   Alan DeKok.
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
 		 	   		  =

--_1de28bcc-3e9d-4f65-87b0-855562c143b3_
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'>
Glancing at -13=2C there appear to be some inconsistencies within the text:=
<br><br>Section 1.3.1<br><br>As RADIUS has become more widely accepted as a=
 management protocol=2C<br>its usage has become more prevalent=2C both with=
in the IETF as well as<br>within other SDOs. Given the expanded utilization=
 of RADIUS=2C it has<br>become apparent that requiring SDOs to accomplish a=
ll their RADIUS<br>work within the IETF is inherently inefficient and unsca=
lable. By<br>articulating guidelines for RADIUS attribute design=2C this do=
cument<br>enables SDOs out of the IETF to design their own RADIUS attribute=
s<br>within the Vendor-Specific Attribute (VSA) space.<br><br>It is RECOMME=
NDED that SDOs follow the guidelines articulated in this<br>document. Howev=
er=2C we recognize that there are some situations where<br>SDOs or vendors =
require the creation of specifications not following<br>these guidelines. W=
e do not forbid these specifications=2C but it is<br>RECOMMENDED that they =
are created only if they have a limited scope<br>of applicability=2C and al=
l new attributes defined in those<br>specifications are VSAs. See Section 3=
=2C below=2C for additional<br>discussion of this topic.<br><br>It is RECOM=
MENDED that SDOs and vendors seek review of RADIUS<br>attribute specificati=
ons from the IETF. However=2C specifications do<br>not require IETF review =
when they satisfy all of the following<br>criteria:<br><br>* are SDO specif=
ic=3B<br><br>* reference attributes from pre-existing IETF or SDO<br>specif=
ications=3B<br><br>* define new attributes only in the VSA space=3B<br><br>=
* use only the "basic data types" (see below) for all VSAs=3B<br><br>* foll=
ow the guidelines given in this document.<br><br>[BA] This text is similar =
to text in Section 3.3.3=2C which leads me to<br>believe that there was an =
editing problem.<br>My suggestion is that the text in 3.3.3 be moved to Sec=
tion 1.3.1.<br><br>3.3.3. SDO Allocations<br><br>Given the expanded utiliza=
tion of RADIUS=2C it has become apparent that<br>requiring SDOs to accompli=
sh all their RADIUS work within the IETF is<br>inherently inefficient and u=
nscalable. Is is therefore RECOMMENDED<br>that SDO RADIUS Attribute specifi=
cations allocate attributes from the<br>vendor space=2C rather than request=
ing an allocation from the RADIUS<br>standard attribute space=2C for attrib=
utes matching any of the<br>following criteria:<br><br>* attributes relying=
 on data types not defined within RADIUS<br><br>* attributes intended prima=
rily for use within an SDO<br><br>* attributes intended primarily for use w=
ithin a group of SDOs.<br><br>Any new RADIUS attributes or values intended =
for interoperable use<br>across a broad spectrum of the Internet Community =
SHOULD follow the<br>allocation process defined in [RFC3575].<br><br>The re=
commendation for SDOs to allocate attributes from a vendor<br>space rather =
than via the IETF process is a recognition that SDOs<br>desire to assert ch=
ange control over their own RADIUS specifications.<br>This change control c=
an be obtained by requesting a PEC from the<br>Internet Assigned Number Aut=
hority (IANA)=2C for use as a Vendor-Id<br>within a Vendor-Specific attribu=
te. The SDO can then allocate<br>attributes within the VSA space defined by=
 that Vendor-Id=2C at their<br>sole discretion. Similarly=2C the use of dat=
a types (complex or<br>otherwise) within that VSA space is solely under the=
 discretion of<br>the SDO.<br><br>Nevertheless=2C following the guidelines =
outlined within this document<br>has many advantages. It is therefore RECOM=
MENDED that SDOs follow<br>the guidelines outlined here=2C which are intend=
ed to enable maximum<br>interoperability with minimal changes to existing s=
ystems.<br><br>[BA] The last paragraph does not appear to be consistent wit=
h Section 1.3=2C<br>so I'd<br>recommend that it be deleted.<br><br>3.3.2. V=
endor Allocations<br><br>Nevertheless=2C following the guidelines outlined =
within this document<br>has many advantages. It is therefore RECOMMENDED th=
at vendors follow<br>the guidelines outlined here=2C which are intended to =
enable maximum<br>interoperability with minimal changes to existing systems=
. If these<br>guidelines are not followed=2C the result will be increased c=
omplexity<br>with little or no benefit.<br><br>[BA] The resolution to Issue=
 327 recommended the following alternative text:<br><br>Nevertheless=2C fol=
lowing the guidelines outlined within this document<br>has several advantag=
es=2C including maximum interoperability with<br>minimal changes to existin=
g systems. Following these guidelines<br>means that RADIUS servers can be u=
pdated to support the vendor's<br>equipment by editing a RADIUS dictionary.=
 If these guidelines are<br>not followed=2C then the vendor's equipment can=
 only be supported<br>via code changes in RADIUS server implementations.<br=
>Such code changes add complexity and delay to implementations."<br><br>3.3=
.4. Publication of specifications<br><br>In order to enable IETF review of =
SDO specifications=2C it is<br>RECOMMENDED that:<br><br>* SDOs make their R=
ADIUS attribute specifications publicly<br>available=3B<br><br>* SDOs reque=
st review of RADIUS attribute specifications by<br>sending email to the AAA=
 Doctors [DOCTORS] or equivalent mailing<br>list=3B<br><br>* IETF and SDO R=
ADIUS attribute specifications are reviewed<br>according to the guidelines =
proposed in this document=3B<br><br>* Reviews of specifications are posted =
to the RADEXT WG mailing<br>list=2C<br>the AAA Doctors mailing list [DOCTOR=
S] or another IETF mailing<br>list<br>suggested by the Operations &amp=3B M=
anagement Area Directors of the<br>IETF.<br><br>It should be understood tha=
t SDOs do not have to rehost VSAs into the<br>standards space solely for th=
e purpose of obtaining IETF review.<br>Rehosting puts pressure on the stand=
ards space=2C and may be harmful to<br>interoperability=2C since it can cre=
ate two ways to provision the same<br>service. Rehosting may also require c=
hanges to the RADIUS data model<br>which will affect implementations that d=
o not intend to support the<br>SDO specifications.<br><br>These reviews can=
 assist with creation of specifications that meet<br>the SDO requirements=
=2C and which are also compatible with the<br>traditional data model and us=
es of RADIUS. While these reviews<br>require access to public specification=
s=2C the review process does not<br>require publication of an IETF RFC.<br>=
<br>SDOs are encouraged to seek early review of their specifications by<br>=
the IETF. It should be understood that reviews are a voluntary-based<br>ser=
vice offered on best-effort basis.<br><br>Where the RADIUS specification is=
 embedded within a larger document<br>which cannot be made public=2C the RA=
DIUS attribute and value<br>definitions SHOULD be published instead as an I=
nformational RFC=2C as<br>with [RFC4679]. This process SHOULD be followed i=
nstead of<br>requesting IANA allocations from within the standard RADIUS at=
tribute<br>space.<br><br>Similarly=2C vendors are encouraged to make their =
specifications<br>publicly available=2C for maximum interoperability. Howev=
er=2C it is not<br>necessary for them to request publication of their VSA s=
pecifications<br>as Informational RFCs by the IETF.<br><br>All other specif=
ications=2C including new authentication=2C<br>authorization=2C and/or secu=
rity mechanisms SHOULD follow the<br>allocation process defined in [RFC3575=
].<br><br>[BA] The resolution to Issue 327 recommended the following altern=
ative text:<br><br>SDOs or vendors desiring review of their RADIUS specific=
ations<br>by the IETF are encouraged to seek review as early as possible=2C=
<br>so as to avoid potential delays. Since reviews are handled by volunteer=
s=2C<br>responses are provided on a best-effort basis=2C with no service<br=
>level guarantees. In order to provide reviewers with access to the<br>spec=
ification=2C SDOs and vendors are encouraged to make them publicly<br>avail=
able.<br>Where the RADIUS specification is embedded within a larger documen=
t which<br>cannot be made public=2C the RADIUS attribute and value definiti=
ons<br>can be made available on a public web site or can be published as<br=
>an Informational RFC=2C as with [RFC4679].<br><br>Review can be requested =
by sending email to the AAA Doctors [DOCTORS]<br>or equivalent mailing list=
. The IETF Operations &amp=3B Management<br>Area Directors will then arrang=
e for the review to be<br>completed and posted to the AAA Doctors mailing l=
ist<br>[DOCTORS]=2C RADEXT WG mailing list=2C or other IETF mailing<br>list=
.<br><br>The review process requires neither allocation of attributes<br>wi=
thin the IETF standard attribute space nor publication of an<br>IETF RFC. R=
equiring SDOs or vendors to rehost VSAs into the IETF standards<br>attribut=
e space solely for the purpose of obtaining review<br>would put pressure on=
 the standards space=2C and may be harmful to<br>interoperability=2C since =
it can create two ways to provision the same<br>service. Rehosting may also=
 require changes to the RADIUS data model<br>which will affect implementati=
ons that do not intend to support the<br>SDO or vendor specifications."<br>=
<br>&gt=3B -----Original Message-----<br>&gt=3B From: owner-radiusext@ops.i=
etf.org [mailto:owner-radiusext@ops.ietf.org] On<br>&gt=3B Behalf Of Alan D=
eKok<br>&gt=3B Sent: Wednesday=2C April 14=2C 2010 5:55 AM<br>&gt=3B To: ra=
diusext@ops.ietf.org<br>&gt=3B Subject: Re: I-D Action:draft-ietf-radext-de=
sign-13.txt<br>&gt=3B <br>&gt=3B Internet-Drafts@ietf.org wrote:<br>&gt=3B =
&gt=3B A New Internet-Draft is available from the on-line Internet-Drafts<b=
r>&gt=3B directories.<br>&gt=3B &gt=3B This draft is a work item of the RAD=
IUS EXTensions Working Group of the<br>&gt=3B IETF.<br>&gt=3B &gt=3B <br>&g=
t=3B &gt=3B <br>&gt=3B &gt=3B 	Title           : RADIUS Design Guidelines<b=
r>&gt=3B &gt=3B 	Author(s)       : G. Weber=2C A. DeKok<br>&gt=3B &gt=3B 	F=
ilename        : draft-ietf-radext-design-13.txt<br>&gt=3B &gt=3B 	Pages   =
        : 40<br>&gt=3B &gt=3B 	Date            : 2010-04-14<br>&gt=3B <br>&=
gt=3B   See also the 'diff' available at:<br>&gt=3B <br>&gt=3B http://tools=
.ietf.org/rfcdiff?url2=3Ddraft-ietf-radext-design-13.txt<br>&gt=3B <br>&gt=
=3B   This revision incorporates suggestions from all open issues=2C includ=
ing<br>&gt=3B #327.<br>&gt=3B <br>&gt=3B   Please provide feedback.<br>&gt=
=3B <br>&gt=3B   Alan DeKok.<br>&gt=3B <br>&gt=3B --<br>&gt=3B to unsubscri=
be send a message to radiusext-request@ops.ietf.org with<br>&gt=3B the word=
 'unsubscribe' in a single line as the message text body.<br>&gt=3B archive=
: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br> 		 	   		  </body>
</html>=

--_1de28bcc-3e9d-4f65-87b0-855562c143b3_--

--
to unsubscribe send a message to radiusext-request@ops.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, 14 Apr 2010 12:55:15 +0000
Message-ID: <4BC5BB10.4080006@deployingradius.com>
Date: Wed, 14 Apr 2010 14:54:40 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: I-D Action:draft-ietf-radext-design-13.txt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the RADIUS EXTensions Working Group of the IETF.
> 
> 
> 	Title           : RADIUS Design Guidelines
> 	Author(s)       : G. Weber, A. DeKok
> 	Filename        : draft-ietf-radext-design-13.txt
> 	Pages           : 40
> 	Date            : 2010-04-14

  See also the 'diff' available at:

http://tools.ietf.org/rfcdiff?url2=draft-ietf-radext-design-13.txt

  This revision incorporates suggestions from all open issues, including
#327.

  Please provide feedback.

  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, 14 Apr 2010 12:26:21 +0000
Message-ID: <4BC5B453.2010802@deployingradius.com>
Date: Wed, 14 Apr 2010 14:25:55 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Proposal for resolution of Issue 327:  Applicability
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:

> [BA] Proposed change is to replace Section 1 with the following:
> 
>    "This document provides guidelines for the design of RADIUS attributes
>    used to encode service-provisioning or authentication data,
>    based on the data model and attribute formats defined in RFC 2865 and
>    subsequent RADIUS RFCs.

  I think that text is better left in the "Applicability" section.  The
introduction should motivate the document, rather than explaining where
it applies.

>   In order to characterize current attribute
>    usage, both the basic and complex data types defined in the existing 
>    RADIUS RFCs are reviewed. Since the RADEXT WG is currently considering
>    extensions to the RADIUS data model and attribute formats,
>    future documents may extend the data model and guidelines provided here.

  The IETF process already allows for future documents.  I'm not sure
that we need to re-state it here.

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

  The current text in the "Applicability" section motivates the
document, rather than explaining the applicability.

  I suggest starting Section 1.3 with a clear statement of
applicability, using the text suggested above.

  I've addressed the rest of the review in -13 (to be submitted
shortly).  Some of the suggestions didn't apply to -12, and some were
added with re-arrangements.

  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, 14 Apr 2010 12:16:26 +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-13.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100414121503.8200128C281@core3.amsl.com>
Date: Wed, 14 Apr 2010 05:15:03 -0700 (PDT)

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : RADIUS Design Guidelines
	Author(s)       : G. Weber, A. DeKok
	Filename        : draft-ietf-radext-design-13.txt
	Pages           : 40
	Date            : 2010-04-14

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

Content-Type: text/plain
Content-ID:     <2010-04-14050415.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, 13 Apr 2010 20:42:34 +0000
Message-ID: <4BC4D71C.3050903@deployingradius.com>
Date: Tue, 13 Apr 2010 22:42:04 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: (repost) Reminder for review of Design Guidelines document
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> The changes made in -12 largely relate to the organizational issues
> brought up by Hannes.

  And others.

> Therefore it would appear that Issue 327 remains open, and possibly some
> of the concerns expressed by Avi and others relating to Issue 325.

  Issue #325 has been addressed in -12.  Issue #327 is being worked on.
 All other concerns are either addressed in -12, or are out of scope of
the document.

> As a result, it would appear that there is still WG consensus against
> publication of the document.

  Given the volume of criticism directed against the document, and the
strong desire that it be re-organized, I would hope that people care
enough to review the -12 version, which directly addresses their
concerns.  If their concerns aren't strong enough to warrant a review of
-12, then I suggest that the concerns aren't serious.

  I will review the text suggested in issue #327 for inclusion in the
next rev of the document.  But the document has changed substantially
since the review was made, and portions of the suggestions are no longer
relevant.

  If there are no other concerns with -12, then I suggest that we do a
-13 addressing issue #327, and call the document "finished".

  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, 13 Apr 2010 19:43:24 +0000
Message-ID: <BLU137-W2335B6060EFAF690A6342093110@phx.gbl>
Content-Type: multipart/alternative; boundary="_0b59c8f2-c3c8-4fd3-9891-257bafc3ef2a_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RE: (repost) Reminder for review of Design Guidelines document
Date: Tue, 13 Apr 2010 12:42:08 -0700
MIME-Version: 1.0

--_0b59c8f2-c3c8-4fd3-9891-257bafc3ef2a_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


The changes made in -12 largely relate to the organizational issues brought=
 up by Hannes.=20

Therefore it would appear that Issue 327 remains open=2C and possibly some =
of the concerns expressed by Avi and others relating to Issue 325.=20

As a result=2C it would appear that there is still WG consensus against pub=
lication of the document.=20

> Date: Tue=2C 13 Apr 2010 16:57:25 +0200
> From: aland@deployingradius.com
> To: radiusext@ops.ietf.org
> Subject: (repost) Reminder for review of Design Guidelines document
>=20
>   We've had one review so far.  More would be better.
>=20
>   The guidelines document was updated significantly to address the open
> concerns.  The latest revision is available at:
>=20
> http://tools.ietf.org/html/draft-ietf-radext-design-12
>=20
>   The high-level differences are an update as per the review from
> Hannes.  The outline is now:
>=20
> introduction	(2 pages)
> guidelines	(3 pages)
> rationale	(11 pages)
>=20
>   The "guidelines" section gives the guidelines with no supporting
> arguments.  All of the arguments are in the "rationale" section.  We
> hope that this organization makes the guidelines easier to understand.
>=20
>   The document still needs some minor editing=2C and also should integrat=
e
> comments from Issue #327.  However=2C these changes are expected to be
> minor=2C and we are looking for feedback on the current draft.
>=20
>   A diff is at:
>=20
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-radext-design-12.txt
>=20
>   The diff isn't that useful=2C as too much has changed.
>=20
>   Alan DeKok.
>=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/>
 		 	   		  =

--_0b59c8f2-c3c8-4fd3-9891-257bafc3ef2a_
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 changes made in -12 largely relate to the organizational issues brought=
 up by Hannes. <br><br>Therefore it would appear that Issue 327 remains ope=
n=2C and possibly some of the concerns expressed by Avi and others relating=
 to Issue 325. <br><br>As a result=2C it would appear that there is still W=
G consensus against publication of the document. <br><br>&gt=3B Date: Tue=
=2C 13 Apr 2010 16:57:25 +0200<br>&gt=3B From: aland@deployingradius.com<br=
>&gt=3B To: radiusext@ops.ietf.org<br>&gt=3B Subject: (repost) Reminder for=
 review of Design Guidelines document<br>&gt=3B <br>&gt=3B   We've had one =
review so far.  More would be better.<br>&gt=3B <br>&gt=3B   The guidelines=
 document was updated significantly to address the open<br>&gt=3B concerns.=
  The latest revision is available at:<br>&gt=3B <br>&gt=3B http://tools.ie=
tf.org/html/draft-ietf-radext-design-12<br>&gt=3B <br>&gt=3B   The high-lev=
el differences are an update as per the review from<br>&gt=3B Hannes.  The =
outline is now:<br>&gt=3B <br>&gt=3B introduction	(2 pages)<br>&gt=3B guide=
lines	(3 pages)<br>&gt=3B rationale	(11 pages)<br>&gt=3B <br>&gt=3B   The "=
guidelines" section gives the guidelines with no supporting<br>&gt=3B argum=
ents.  All of the arguments are in the "rationale" section.  We<br>&gt=3B h=
ope that this organization makes the guidelines easier to understand.<br>&g=
t=3B <br>&gt=3B   The document still needs some minor editing=2C and also s=
hould integrate<br>&gt=3B comments from Issue #327.  However=2C these chang=
es are expected to be<br>&gt=3B minor=2C and we are looking for feedback on=
 the current draft.<br>&gt=3B <br>&gt=3B   A diff is at:<br>&gt=3B <br>&gt=
=3B http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-radext-design-12.txt<br=
>&gt=3B <br>&gt=3B   The diff isn't that useful=2C as too much has changed.=
<br>&gt=3B <br>&gt=3B   Alan DeKok.<br>&gt=3B <br>&gt=3B <br>&gt=3B --<br>&=
gt=3B to unsubscribe send a message to radiusext-request@ops.ietf.org with<=
br>&gt=3B the word 'unsubscribe' in a single line as the message text body.=
<br>&gt=3B archive: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br> 		 	   =
		  </body>
</html>=

--_0b59c8f2-c3c8-4fd3-9891-257bafc3ef2a_--

--
to unsubscribe send a message to radiusext-request@ops.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, 13 Apr 2010 14:58:18 +0000
Message-ID: <4BC48655.4070504@deployingradius.com>
Date: Tue, 13 Apr 2010 16:57:25 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: (repost) Reminder for review of Design Guidelines document
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

  We've had one review so far.  More would be better.

  The guidelines document was updated significantly to address the open
concerns.  The latest revision is available at:

http://tools.ietf.org/html/draft-ietf-radext-design-12

  The high-level differences are an update as per the review from
Hannes.  The outline is now:

introduction	(2 pages)
guidelines	(3 pages)
rationale	(11 pages)

  The "guidelines" section gives the guidelines with no supporting
arguments.  All of the arguments are in the "rationale" section.  We
hope that this organization makes the guidelines easier to understand.

  The document still needs some minor editing, and also should integrate
comments from Issue #327.  However, these changes are expected to be
minor, and we are looking for feedback on the current draft.

  A diff is at:

http://tools.ietf.org/rfcdiff?url2=draft-ietf-radext-design-12.txt

  The diff isn't that useful, as too much has changed.

  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, 07 Apr 2010 05:17:26 +0000
Message-ID: <BLU137-DS4558D2B9C8D745F1CDB3B93170@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Draft minutes of IETF 77 RADEXT WG meeting
Date: Tue, 6 Apr 2010 22:16:44 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007E_01CAD5D6.D7C15610"
Thread-Index: AcrWEYOpSdBfdz+kTPe8fOmcntkrKg==
Content-Language: en-us

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

RADEXT WG Minutes

IETF 77

Anaheim, California USA

Working <http://tools.ietf.org/wg/radext/>  Group Home Page

Jabber room:  radext at jabber.ietf.org

Chairs
        Bernard Aboba <bernard_aboba at hotmail.com
<mailto:bernard_aboba%20at%20hotmail.com> > 
        David Nelson <d.b.nelson at Comcast.net
<mailto:d.b.nelson@comcast.net> >

Agenda
March 22, 2010
 
17:40 - 17:50 PT: Preliminaries 
 
     Bluesheets
     Attendance
     Note takers
     Agenda bash
     Document Status
 
RADEXT WG Agenda Slides
 
Document Status:
 
l  Completed IETF Last Call: Waiting for Revision
l  Design Guidelines <http://tools.ietf.org/html/draft-ietf-radext-design>  
l  In IETF Last Call
l  Status-Server
<http://tools.ietf.org/html/draft-ietf-radext-status-server>  
Comments so far:  An editorial NIT
(http://www.mail-archive.com/ietf@ietf.org/msg45725.html ), and a Gen-Art
review (http://www.ietf.org/mail-archive/web/radext/current/msg01590.html )
l   AD Review: Waiting for Revision 
l  RADIUS over TCP
<http://tools.ietf.org/html/draft-ietf-radext-tcp-transport> 
AD review comments: 
l  Completed RADEXT WG last call: Waiting for PROTO Writeup 
l  New Tunnel Type Values
<http://tools.ietf.org/html/draft-tiwari-radext-tunnel-type>  
l  In RADEXT WG Last Call
l  IPv6 RADIUS attributes
<http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-dhcp-00>  
l  RADIUS over TLS <http://tools.ietf.org/html/draft-ietf-radext-radsec>  
l  RADEXT WG Work Items
l  NAI-based Peer Discovery
<http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery>  
l  RADIUS Crypto-agility Requirements
<http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements>  
l  Extended RADIUS Attributes
<http://tools.ietf.org/html/draft-ietf-radext-extended-attributes>  
l  Under Review as a RADEXT WG Work Item
l  RADIUS Attributes for IEEE 802 Networks
<http://tools.ietf.org/html/draft-aboba-radext-wlan>  
l  RADIUS over DTLS <http://tools.ietf.org/html/draft-dekok-radext-dtls> 
 
 
SECURE RADIUS TRANSPORT (30 minutes)
 
1750 - 1800 AM PT  RTLS, Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec
 
 
RADIUS over TLS Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-2.pdf> 
 
Stefan Winter: We have incorporated proposed resolutions for all open issues
in the tracker within the latest version (-06
<http://tools.ietf.org/html/draft-ietf-radext-radsec-06> ). The document is
ready for another WG last call.
Bernard Aboba: We have started another WG last call (see
http://www.ietf.org/mail-archive/web/radext/current/msg01578.html ).  This
will go until April 19, 2010.  Please read the document and send your review
to the list. 
 
1800 AM - 1810 PT NAI-Based Peer Discovery, Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery
 
 
RADIUS NAI Discovery Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-4.pdf> 
 
Stefan Winter:  Several open issues:
.         S-NAPTR. 
.         Include Diameter?
.         Reference RFC 4282?
.         Guidance on connection attempts (IPv4 vs. IPv6)
 
Alan DeKok:  RFC 4282 is badly broken.  
Bernard Aboba:  Agreed. My advice is to avoid referencing it.  Instead, you
can just reference IDNAbis and tell people to convert U-labels to A-labels
prior to sending DNS queries.  
Hannes Tschofenig: Why are you using S-NAPTR?  Wouldn't it be easier to use
U-NAPTR and a AAA URI?
Stefan Winter:  U-NAPTR might be simpler, if we could utilize the AAA URI
scheme. 
Bernard Aboba: Was Diameter peer discovery ever implemented?
Hannes Tschofenig:  No. 
Bernard Aboba:  Might make sense to explore whether we can come up with a
single solution for Diameter and RADIUS.  Perhaps this should be brought up
in DIME. 
Stefan Winter:  Recommend we stay out of the IPv4 vs. IPv6 issue. 
Bernard Aboba: Big issue so far has been IPv6 blackholing.  Typical causes
are broken tunnels, problems in IPv6 routing, or lack of connectivity
between Teredo/6to4 and native IPv6 Internet.  These problems are more
likely to show up in consumer deployments than in AAA infrastructure.  So it
seems less likely that AAA will need things like DNS IPv6 whitelisting and
perhaps it doesn't matter.  
 
1810 - 1820 PT RADIUS over DTLS, Alan DeKok     (10 minutes)
http://tools.ietf.org/html/draft-dekok-radext-dtls
 
 
RADIUS over DTLS Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-3.ppt> 
 
Alan DeKok:  Major new content in -02. One of the major differences between
RADIUS over TLS and RADIUS over DTLS is that DTLS uses the existing RADIUS
ports.  So you have DTLS and conventional RADIUS being sent to the same port
and the RADIUS implementation has to distinguish DTLS from regular RADIUS
packets.  This is done by looking at the first byte of the RADIUS packet.
If the first byte is 22, then the packet is DTLS, not RADIUS.  For a given 5
tuple (IP Destination address, IP source address, destination port, source
port, UDP), there can only be one choice (DTLS or conventional RADIUS).
This can be implemented on the server in multiple ways.  The server can keep
state in memory relating to whether DTLS or conventional RADIUS was received
on a given 5 tuple.  Or it can keep state in stable storage.  Once DTLS is
received from a given NAS, it can be assumed that the NAS has been upgraded,
and after that, DTLS will always be assumed/required.  The stable storage
approach prevents downgrade attacks after a reboot.
Alan DeKok:  The RADIUS over DTLS document references the RTLS specification
were appropriate, and provides deltas to it.  So the RDTLS document has a
dependency on the RTLS document, but not the other way around.  This makes
since, RADIUS over DTLS implementations are behind RADIUS over TLS by a few
years. 
Stefan Winter: We looked at combining the RADIUS over TLS and RADIUS over
DTLS documents.  However, the documents were at varying levels of maturity
(RTLS has been out for a while, there are multiple interoperable
implementations, DTLS is not yet there), so we didn't think it made sense.
Bernard Aboba: Have there been bakeoffs yet to demonstrate RADIUS over DTLS
interoperability?
Alan DeKok:  Not yet. 
 
 
IPv6 (20 minutes)
 
1820 - 1830  RADIUS Attributes for IPv6 Networks, W. Dec (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-ipv6-access
 
RADIUS Attributes for IPv6 Access Networks Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-6.ppt> 
 
Bernard Aboba:  This document is currently in RADEXT WG last call (see
announcement:
http://www.ietf.org/mail-archive/web/radext/current/msg01547.html  ).  Last
call ended yesterday (March 21, 2010).  However, we only received a few
comments, so will extend last call for a few weeks after IETF 77 to allow
for additional reviews.  Please read the document and send your reviews to
the list, even if it's only to say that the document is fine.  It's not very
long. 
W. Dec:  With early versions of the document, there were concerns about
whether we were trying to create a protocol to handle generic support of
DHCP within RADIUS with no authentication involved.  That is not the
purpose;  we added Section 2 to describe the scenarios. 
 Bernard Aboba:  The protocol exchanges described in the Virtual Interim
(e.g. use of DHCPv6 for configuration and address assignment over PPP
instead of IPv6CP and RA) aren't in Section 2. It would help to refer to
them so that it is clear that authentication is always expected to occur, as
required in RFC 2865.  
W. Dec:  We have received comments in WG last call from Peter Deacon,
relating to existing practices (e.g. how existing implementations use a
combination of Framed-IPv6-Prefix and Framed-Interface-Id to denote an IPv6
address).  The draft describes how a single attribute IPv6-Framed-Address,
can be used in an Accounting-Request, but it doesn't update RFC 3162, so
that attributes allowed in Accounting-Request messages are still legal.  
Alan DeKok:  Shouldn't IPv6-Framed-Address be Framed-IPv6-Address?
 
1830 - 1840  Accounting Extensions for IPv6, R. Maglione (10 minutes)
http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions
 
RADIUS Accounting for IPv6 Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-5.ppt> 
 
There have been a number of review comments on the list. 
>From Avi Lior: http://ops.ietf.org/lists/radiusext/2010/msg00193.html
(Existing attributes are not just for IPv4, they count both IPv4 and IPv6).

Alan DeKok: http://ops.ietf.org/lists/radiusext/2010/msg00220.html (suggest
sending two Accounting-Requests, one for IPv4 and another for IPv6 (using
existing attributes).  Distinguish the accounting streams based on use of
NAS-IP-Address/NAS-IPv6-Address attributes.  Use Acct-Multi-Session-Id used
to link the two streams together.  This approach  seems operationally too
heavy for both the BRAS and the RADIUS system.  Defining new attributes
appears a simpler solution, and doesn't require changing the meaning of
existing attributes (which appear to apply to both IPv4 and IPv6).  
Bernard Aboba:  Changing the meaning of existing accounting attributes based
on the presence of another attribute (NAS-IP-Address/NAS-IPv6-Address) would
represent a "polymorphic attribute" approach, which is discouraged in Design
Guidelines.  The approach of defining new attributes avoid this problem.  
 
Design Guidelines (50 minutes)
 
1840  - 1930  Design Guidelines, Alan DeKok     (50 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines
 
RADIUS Design Guidelines Presentation
<http://www.ietf.org/proceedings/10mar/slides/radext-1.ppt> 
 
Alan DeKok:  People have commented on the background of the slides.
Bernard Aboba:  About the flames? 
Alan DeKok:  Yes. 
Bernard Aboba:  Here is where we are on Design Guidelines. With respect to
the Last Look, a summary was sent to the RADEXT WG list on January 28, 2010:
http://www.ietf.org/mail-archive/web/radext/current/msg01472.html
 
As described in the summary, the chairs believe that there is WG consensus
against publication of the Design Guidelines document in its current form.
Therefore, the document cannot be advanced until the issues are addressed. 
 
Three issues were opened against the document as a result of the "Last
Look".  One issue was opened by Hannes Tschofenig, relating to the
organization of the document (see
http://www.ietf.org/mail-archive/web/radext/current/msg01515.html ).  
Alan DeKok:  I believe that this issue is resolved in -12
<http://tools.ietf.org/html/draft-ietf-radext-design> . 
 
Another is Issue 325 (opened by Joe Salowey), which relates to the text on
complex attributes.  The issues relates to problems with both the statements
of fact (relating to whether code changes are required in certain
situations) as well as the recommendations.   Changes were made in -11 and
-12 to resolve this issue. Joe has indicated that the suggested changes were
helpful (see
http://www.ietf.org/mail-archive/web/radext/current/msg01434.html), so I am
going to close the issue. 
 
Since other "Last Look" comments appear to indicate that the changes are
insufficient, it is possible that there are additional changes required, but
we don't have specific comments or text changes on the table. How do we move
forward? 
Alan DeKok: I will solicit feedback on the list (done, see
http://www.ietf.org/mail-archive/web/radext/current/msg01588.html ). 
Bernard Aboba:  If you have concerns relating to the text on complex
attributes, please submit specific changes to the list.  The time for
general comments is past. This document has completed WG last call and IETF
last call and IESG DISCUSS comments have been resolved.  We need text to
move forward.  
 
On Issue 327 (opened as a result of postings by Avi Lior), a proposal for
resolution was made and discussed at the Virtual Interim (see
http://www.ietf.org/mail-archive/web/radext/current/msg01496.html )  Avi
accepted the resolution, but the suggested resolution has not yet been
reflected in the document. 
Alan DeKok:  In -12 I focused on improving document readability.  Since
there were so many editorial changes to the document, the proposal no longer
applied.
Bernard Aboba:  I will take an action item to resubmit the proposed
resolution, based on the -12 organization.  However, I do not believe that
Issue 327 has been resolved, so I will not close it. 
 
Wrap-up (10 minutes)
 
1930 - 1940  Discussion and Next Steps:  WG Chairs & ADs (10 minutes)

 


------=_NextPart_000_007E_01CAD5D6.D7C15610
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Times;
	panose-1:2 2 6 3 5 4 5 2 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	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.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";}
.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;}
 /* List Definitions */
 @list l0
	{mso-list-id:547448458;
	mso-list-type:hybrid;
	mso-list-template-ids:791336830 -1792493236 267138734 -55679474 =
-1271366590 -2118354756 801817786 -1204915546 -1132534694 -627147322;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F06C;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level2
	{mso-level-start-at:887;
	mso-level-number-format:bullet;
	mso-level-text:\F06C;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level3
	{mso-level-start-at:887;
	mso-level-number-format:bullet;
	mso-level-text:\F06C;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1168910503;
	mso-list-type:hybrid;
	mso-list-template-ids:-1264437688 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</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'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal'><b><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>RADEXT
WG Minutes</span></b><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;
line-height:normal'><b><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>IETF
77</span></b><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;
line-height:normal'><b><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Anaheim,
California USA</span></b><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;margin-bottom:12.0pt;
line-height:normal'><a name=3Dwg-martini></a><span =
style=3D'font-size:10.0pt;
font-family:"Times","serif"'><a =
href=3D"http://tools.ietf.org/wg/radext/">Working
Group Home Page</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;margin-bottom:12.0pt;
line-height:normal'><span =
style=3D'font-size:10.0pt;font-family:"Times","serif"'>Jabber
room:&nbsp; radext at jabber.ietf.org<br>
<br>
Chairs<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Bernard Aboba &lt;<a
href=3D"mailto:bernard_aboba%20at%20hotmail.com">bernard_aboba at =
hotmail.com</a>&gt;
<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; David Nelson &lt;<a
href=3D"mailto:d.b.nelson@comcast.net">d.b.nelson at =
Comcast.net</a>&gt;</span><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<pre>Agenda<o:p></o:p></pre><pre>March 22, =
2010<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>17:40 &#8211; =
17:50 PT: Preliminaries =
<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp=
; Bluesheets<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp; =
Attendance<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp; Note =
takers<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp; Agenda =
bash<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp; Document =
Status<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><u><span
style=3D'font-family:"Arial","sans-serif";color:blue'>RADEXT WG Agenda =
Slides</span></u><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Docume=
nt Status:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>Completed IETF Last Call: Waiting for =
Revision<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design">Design =
Guidelines</a> <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>In IETF Last Call<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">Statu=
s-Server</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in'>Comments so far:&nbsp; An editorial NIT (<a
href=3D"http://www.mail-archive.com/ietf@ietf.org/msg45725.html">http://w=
ww.mail-archive.com/ietf@ietf.org/msg45725.html</a> ), and a Gen-Art =
review (<a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01590.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01590.html</a> =
)<o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>&nbsp;AD Review: Waiting for Revision =
<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport">RADIU=
S over TCP</a><o:p></o:p></pre><pre
style=3D'margin-left:1.0in'>AD review comments: <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>Completed RADEXT WG last call: Waiting =
for PROTO Writeup <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-tiwari-radext-tunnel-type">New =
Tunnel Type Values</a> <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>In RADEXT WG Last =
Call<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-dhcp-00">I=
Pv6 RADIUS attributes</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">RADIUS over =
TLS</a> <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>RADEXT WG Work Items<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">N=
AI-based Peer Discovery</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requi=
rements">RADIUS Crypto-agility Requirements</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-extended-attributes"=
>Extended RADIUS Attributes</a> <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]>Under Review as a RADEXT WG Work =
Item<o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-aboba-radext-wlan">RADIUS =
Attributes for IEEE 802 Networks</a> <o:p></o:p></pre><pre
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span
style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>l<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span></span><![endif]><a
href=3D"http://tools.ietf.org/html/draft-dekok-radext-dtls">RADIUS over =
DTLS</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:=
p></pre><pre>SECURE RADIUS TRANSPORT (30 =
minutes)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1750 &#8211; =
1800 AM PT&nbsp; RTLS, Stefan Winter (10 =
minutes)<o:p></o:p></pre><pre><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></pre><pre><o:p>&nb=
sp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-2.pdf">RADIUS=
 over TLS Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre>Stefan Winter: We have incorporated proposed resolutions for all =
open issues in the tracker within the latest version (<a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec-06">-06</a>).=
 The document is ready for another WG last =
call.<o:p></o:p></pre><pre>Bernard Aboba: We have started another WG =
last call (see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01578.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01578.html</a> =
).&nbsp; This will go until April 19, 2010.&nbsp; Please read the =
document and send your review to the list. =
<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>1800 AM - 1810 PT =
NAI-Based Peer Discovery, Stefan Winter (10 =
minutes)<o:p></o:p></pre><pre><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></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><sp=
an
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-4.pdf">RADIUS=
 NAI Discovery Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre>Stefan Winter:&nbsp; Several open issues:<o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>S-NAPTR. <o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Include Diameter?<o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Reference RFC 4282?<o:p></o:p></pre><pre
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Guidance on connection attempts (IPv4 vs. =
IPv6)<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Alan DeKok:&nbsp; =
RFC 4282 is badly broken.&nbsp; <o:p></o:p></pre><pre>Bernard =
Aboba:&nbsp; Agreed. My advice is to avoid referencing it.&nbsp; =
Instead, you can just reference IDNAbis and tell people to convert =
U-labels to A-labels prior to sending DNS queries.&nbsp; =
<o:p></o:p></pre><pre>Hannes Tschofenig: Why are you using =
S-NAPTR?&nbsp; Wouldn&#8217;t it be easier to use U-NAPTR and a AAA =
URI?<o:p></o:p></pre><pre>Stefan Winter:&nbsp; U-NAPTR might be simpler, =
if we could utilize the AAA URI scheme. <o:p></o:p></pre><pre>Bernard =
Aboba: Was Diameter peer discovery ever =
implemented?<o:p></o:p></pre><pre>Hannes Tschofenig:&nbsp; No. =
<o:p></o:p></pre><pre>Bernard Aboba:&nbsp; Might make sense to explore =
whether we can come up with a single solution for Diameter and =
RADIUS.&nbsp; Perhaps this should be brought up in DIME. =
<o:p></o:p></pre><pre>Stefan Winter:&nbsp; Recommend we stay out of the =
IPv4 vs. IPv6 issue. <o:p></o:p></pre><pre>Bernard Aboba: Big issue so =
far has been IPv6 blackholing.&nbsp; Typical causes are broken tunnels, =
problems in IPv6 routing, or lack of connectivity between Teredo/6to4 =
and native IPv6 Internet.&nbsp; These problems are more likely to show =
up in consumer deployments than in AAA infrastructure.&nbsp; So it seems =
less likely that AAA will need things like DNS IPv6 whitelisting and =
perhaps it doesn&#8217;t matter.&nbsp; =
<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1810 &#8211; 1820 PT =
RADIUS over DTLS, Alan DeKok&nbsp;&nbsp;&nbsp;&nbsp; (10 =
minutes)<o:p></o:p></pre><pre><a
href=3D"http://tools.ietf.org/html/draft-dekok-radext-dtls">http://tools.=
ietf.org/html/draft-dekok-radext-dtls</a><o:p></o:p></pre><pre><o:p>&nbsp=
;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-3.ppt">RADIUS=
 over DTLS Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre>Alan DeKok:&nbsp; Major new content in -02. One of the major =
differences between RADIUS over TLS and RADIUS over DTLS is that DTLS =
uses the existing RADIUS ports.&nbsp; So you have DTLS and conventional =
RADIUS being sent to the same port and the RADIUS implementation has to =
distinguish DTLS from regular RADIUS packets.&nbsp; This is done by =
looking at the first byte of the RADIUS packet.&nbsp; If the first byte =
is 22, then the packet is DTLS, not RADIUS.&nbsp; For a given 5 tuple =
(IP Destination address, IP source address, destination port, source =
port, UDP), there can only be one choice (DTLS or conventional =
RADIUS).&nbsp; This can be implemented on the server in multiple =
ways.&nbsp; The server can keep state in memory relating to whether DTLS =
or conventional RADIUS was received on a given 5 tuple.&nbsp; Or it can =
keep state in stable storage.&nbsp; Once DTLS is received from a given =
NAS, it can be assumed that the NAS has been upgraded, and after that, =
DTLS will always be assumed/required.&nbsp; The stable storage approach =
prevents downgrade attacks after a reboot.<o:p></o:p></pre><pre>Alan =
DeKok:&nbsp; The RADIUS over DTLS document references the RTLS =
specification were appropriate, and provides deltas to it.&nbsp; So the =
RDTLS document has a dependency on the RTLS document, but not the other =
way around.&nbsp; This makes since, RADIUS over DTLS implementations are =
behind RADIUS over TLS by a few years. <o:p></o:p></pre><pre>Stefan =
Winter: We looked at combining the RADIUS over TLS and RADIUS over DTLS =
documents.&nbsp; However, the documents were at varying levels of =
maturity (RTLS has been out for a while, there are multiple =
interoperable implementations, DTLS is not yet there), so we =
didn&#8217;t think it made sense.<o:p></o:p></pre><pre>Bernard Aboba: =
Have there been bakeoffs yet to demonstrate RADIUS over DTLS =
interoperability?<o:p></o:p></pre><pre>Alan DeKok:&nbsp; Not yet. =
<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp;<o:p></o:p></pre>=
<pre>IPv6 (20 =
minutes)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1820 &#8211; =
1830 &nbsp;RADIUS Attributes for IPv6 Networks, W. Dec (10 =
minutes)<o:p></o:p></pre><pre><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-ipv6-access">http://=
tools.ietf.org/html/draft-ietf-radext-ipv6-access</a><o:p></o:p></pre><pr=
e><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-6.ppt">RADIUS=
 Attributes for IPv6 Access Networks =
Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; This =
document is currently in RADEXT WG last call (see announcement:</span> =
<span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01547.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01547.html</a>&n=
bsp; ).&nbsp; Last call ended yesterday (March 21, 2010).&nbsp; However, =
we only received a few comments, so will extend last call for a few =
weeks after IETF 77 to allow for additional reviews.&nbsp; Please read =
the document and send your reviews to the list, even if it&#8217;s only =
to say that the document is fine.&nbsp; It&#8217;s not very long. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>W. Dec:&nbsp; With early =
versions of the document, there were concerns about whether we were =
trying to create a protocol to handle generic support of DHCP within =
RADIUS with no authentication involved.&nbsp; That is not the =
purpose;&nbsp; we added Section 2 to describe the scenarios. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>&nbsp;Bernard Aboba:&nbsp; =
The protocol exchanges described in the Virtual Interim (e.g. use of =
DHCPv6 for configuration and address assignment over PPP instead of =
IPv6CP and RA) aren&#8217;t in Section 2. It would help to refer to them =
so that it is clear that authentication is always expected to occur, as =
required in RFC 2865.&nbsp; <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>W. Dec:&nbsp; We have =
received comments in WG last call from Peter Deacon, relating to =
existing practices (e.g. how existing implementations use a combination =
of Framed-IPv6-Prefix and Framed-Interface-Id to denote an IPv6 =
address).&nbsp; The draft describes how a single attribute =
IPv6-Framed-Address, can be used in an Accounting-Request, but it =
doesn&#8217;t update RFC 3162, so that attributes allowed in =
Accounting-Request messages are still legal.&nbsp; =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; =
Shouldn&#8217;t IPv6-Framed-Address be =
Framed-IPv6-Address?<o:p></o:p></span></pre><pre>&nbsp;<o:p></o:p></pre><=
pre>1830 - 1840 &nbsp;Accounting Extensions for IPv6, R. Maglione (10 =
minutes)<o:p></o:p></pre><pre><a
href=3D"http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extens=
ions">http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensio=
ns</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-5.ppt">RADIUS=
 Accounting for IPv6 Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>There have been =
a number of review comments on the list. =
<o:p></o:p></span></pre><pre><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>From Avi Lior: =
<a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00193.html">http://op=
s.ietf.org/lists/radiusext/2010/msg00193.html</a>&nbsp; (Existing =
attributes are not just for IPv4, they count both IPv4 and IPv6).&nbsp; =
<o:p></o:p></span></pre><pre><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>Alan DeKok: <a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00220.html">http://op=
s.ietf.org/lists/radiusext/2010/msg00220.html</a> (suggest sending two =
Accounting-Requests, one for IPv4 and another for IPv6 (using existing =
attributes).&nbsp; Distinguish the accounting streams based on use of =
NAS-IP-Address/NAS-IPv6-Address attributes.&nbsp; Use </span><i><span
style=3D'font-family:"Arial","sans-serif"'>Acct-Multi-Session-Id =
</span></i><span
style=3D'font-family:"Arial","sans-serif"'>used to link the two streams =
together.&nbsp; </span><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>This =
approach&nbsp; seems operationally too heavy for both the BRAS and the =
RADIUS system.&nbsp; Defining new attributes appears a simpler solution, =
and doesn&#8217;t require changing the meaning of existing attributes =
(which appear to apply to both IPv4 and IPv6).&nbsp; =
<o:p></o:p></span></pre><pre><span
lang=3DEN-GB style=3D'font-family:"Arial","sans-serif"'>Bernard =
Aboba:&nbsp; Changing the meaning of existing accounting attributes =
based on the presence of another attribute =
(NAS-IP-Address/NAS-IPv6-Address) would represent a &#8220;polymorphic =
attribute&#8221; approach, which is discouraged in Design =
Guidelines.&nbsp; The approach of defining new attributes avoid this =
problem.&nbsp; =
<o:p></o:p></span></pre><pre>&nbsp;<o:p></o:p></pre><pre>Design =
Guidelines (50 =
minutes)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1840 =
&nbsp;&#8211; 1930 &nbsp;Design Guidelines, Alan =
DeKok&nbsp;&nbsp;&nbsp;&nbsp; (50 minutes)<o:p></o:p></pre><pre><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></pre><pre><o:p>&nbsp;</o:p></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/proceedings/10mar/slides/radext-1.ppt">RADIUS=
 Design Guidelines Presentation</a><o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; People have =
commented on the background of the =
slides&#8230;<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; About =
the flames? <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; Yes. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; Here is =
where we are on Design Guidelines. With respect to the Last Look, a =
summary was sent to the RADEXT WG list on January 28, =
2010:<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01472.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01472.html</a><o=
:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>As described in the summary, =
the chairs believe that there is WG consensus against publication of the =
Design Guidelines document in its current form.&nbsp; Therefore, the =
document cannot be advanced until the issues are addressed. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Three issues were opened =
against the document as a result of the &#8220;Last Look&#8221;.&nbsp; =
One issue was opened by Hannes Tschofenig, relating to the organization =
of the document (see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01515.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01515.html</a> =
).&nbsp; <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; I believe =
that this issue is resolved in <a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design">-12</a>. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Another is Issue 325 (opened =
by Joe Salowey), which relates to the text on complex attributes.&nbsp; =
The issues relates to problems with both the statements of fact =
(relating to whether code changes are required in certain situations) as =
well as the recommendations.&nbsp;&nbsp; Changes were made in -11 and =
-12 to resolve this issue. Joe has indicated that the suggested changes =
were helpful (see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01434.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01434.html</a>),=
 so I am going to close the issue. <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>Since other &#8220;Last =
Look&#8221; comments appear to indicate that the changes are =
insufficient, it is possible that there are additional changes required, =
but we don&#8217;t have specific comments or text changes on the table. =
How do we move forward? <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok: I will solicit =
feedback on the list (done, see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01588.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01588.html</a> =
). <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; If you =
have concerns relating to the text on complex attributes, please submit =
specific changes to the list.&nbsp; The time for general comments is =
past. This document has completed WG last call and IETF last call and =
IESG DISCUSS comments have been resolved.&nbsp; We need text to move =
forward.&nbsp; <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre>=
<pre><span
style=3D'font-family:"Arial","sans-serif"'>On Issue 327 (opened as a =
result of postings by Avi Lior), a proposal for resolution was made and =
discussed at the Virtual Interim (see <a
href=3D"http://www.ietf.org/mail-archive/web/radext/current/msg01496.html=
">http://www.ietf.org/mail-archive/web/radext/current/msg01496.html</a> =
)&nbsp; Avi accepted the resolution, but the suggested resolution has =
not yet been reflected in the document. =
<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Alan DeKok:&nbsp; In -12 I =
focused on improving document readability.&nbsp; Since there were so =
many editorial changes to the document, the proposal no longer =
applied.<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Arial","sans-serif"'>Bernard Aboba:&nbsp; I will =
take an action item to resubmit the proposed resolution, based on the =
-12 organization.&nbsp; However, I do not believe that Issue 327 has =
been resolved, so I will not close it. =
<o:p></o:p></span></pre><pre>&nbsp;<o:p></o:p></pre><pre>Wrap-up (10 =
minutes)<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>1930 - 1940 =
&nbsp;Discussion and Next Steps:&nbsp; WG Chairs &amp; ADs (10 =
minutes)<o:p></o:p></pre>

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

</div>

</body>

</html>

------=_NextPart_000_007E_01CAD5D6.D7C15610--

--
to unsubscribe send a message to radiusext-request@ops.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, 02 Apr 2010 00:32:06 +0000
Message-ID: <BLU137-DS1300A51C213E6DADCD09DD931C0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: FW: review of draft-ietf-radext-status-server-06.txt
Date: Thu, 1 Apr 2010 17:31:58 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcrRqmrNy4lT1majTsu96vl6O371+gAUXYuA
Content-Language: en-us

-----Original Message-----
From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr] 
Sent: Thursday, April 01, 2010 7:48 AM
To: gen-art@ietf.org
Cc: draft-ietf-radext-status-server.all@tools.ietf.org
Subject: review of draft-ietf-radext-status-server-06.txt

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-radext-status-server-06.txt
Reviewer: Francis Dupont
Review Date: 2010-03-28
IETF LC End Date: 2010-03-29
IESG Telechat date: unknown

Summary: Ready with nits

Major issues: none

Minor issues: none

Nits/editorial comments:
 - Abstract page 2: there is an explicit reference to a RFC, this is in
  general forbidden but IMHO we are here in the allowed exception case.

 - 2.1.1 page 8: a servers policy -> a server policy

 - 3 page 10 (twice): etc. -> etc., ???

 - 4.2 page 13: adminstrators -> administrators

 - 4.2 page 15 (twice): e.g. -> e.g.,

 - 4.3 page 16: modelled -> modeled

 - 4.3 page 16: usually the hysteresis against flapping tries to keep
  the connection (i.e., failover after 3 missed responses), here it is
  the opposite. IMHO it is very aggressive but it is how RFC 3539 works
  so I have no concern about it.

 - 4.5 page 16: Proxyhas -> Proxy has

 - 4.5 page 17: cannot, -> cannot

 - 4.5 page 18: i.e. -> i.e.,

 - 5 page 19: EAP-MEssage -> EAP-Message

 - 8 page 23: synthesise -> synthesize

 - 8 page 23: in "the suggestion of [RFC5080] Section 2.2.2, which suggests"
  suggests -> proposes

 - 8 page 23: configurably is not in my dict?

 - 9.2 page 23: IMHO the RFC2119 reference should be moved to normative
  references section (perhaps others too?)

 - Authors' Addresses -> Author's Address

Regards

Francis.Dupont@fdupont.fr

PS: I apologize for the delay. BTW I've seen a wording comment and proposal
from Bernard Aboba, I support it.


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

