Subject: draft-zorn-radius-encattr-15: Obsolete?

From: "Hannes Tschofenig" <[email-masked]>
Date: Fri, 27 Mar 2009 13:58:52 -0700

After the presentation today I took a look at the draft. 

I was wondering whether the work on draft-zorn-radius-encattr-15 became
obsolete with the emergency work on RADSEC? (In more recent terms, this
seems to be a case of overtaken by events (OBE).)

draft-zorn-radius-encattr-15 is a pretty complex piece of work and a custom
solution. The benefits of using TLS/DTLS appear to be much larger. 

Ciao
Hannes

--
to unsubscribe send a message to [email-masked] with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

---

From: "Glen Zorn" <[email-masked]>
Date: Wed, 1 Apr 2009 10:39:29 +0700

Hannes Tschofenig [mailto://[email-masked]] writes:

> draft-zorn-radius-encattr-15 is a pretty complex piece of work and a
> custom solution. 

Not sure what this means.

> The benefits of using TLS/DTLS appear to be much larger.

Perhaps; OTOH, draft-zorn-radius-encattr-15 doesn't require the wholesale
replacement of the existing RADIUS infrastructure.

...

Delivery-date: Mon, 30 Mar 2009 17:56:45 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>
Subject: Re: Use of Framed-IP-Netmask to configure routers
Date: Mon, 30 Mar 2009 10:55:57 -0700

--_2d0f8803-c235-44c3-ab8c-a0a23e7d32c3_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

RFC 2865=2C Section 5.9 defines Framed-IP-Netmask:

This Attribute indicates the IP netmask to be configured for the
      user when the user is a router to a network.  It MAY be used in
      Access-Accept packets.  It MAY be used in an Access-Request packet
      as a hint by the NAS to the server that it would prefer that
      netmask=2C but the server is not required to honor the hint.

In contrast=2C Section 5.22 defines Framed-Route as the mechanism for confi=
guring routing information:

This Attribute provides routing information to be configured for
      the user on the NAS.  It is used in the Access-Accept packet and
      can appear multiple times.

Based on this=2C it would appear that Framed-IP-Netmask is intended for con=
figuration of hosts=2C not routers=2C and that Framed-Route is to be used t=
o configure routes.=20

Defining two mechanisms for configuration of routes seems like it could cre=
ate potential interoperability problems.  Since RFC 2865 is a Draft Standar=
d=2C the existing mechanisms are known to be interoperable.=20

> Pasi made a comment regarding the DISCUSS about RFC2865 that says:
> > * RFC 2865=2C by defining new interpretations of the Framed-IP-Address=
=20
> > and Framed-IP-Netmask attributes.
>=20
>=20
>=20
> Would adding this text clarify (and remove your concerns with) Section
> > 8.2.2?
> >=20
> > @@ -1551=2C7 +1551=2C14 @@
> >     attributes [RFC2865] may be used by the Softwire Concentrator to
> >     delegate an IPv4 prefix to the Softwire Initiator.
> >=20
> > +   As this practice had been used=2C the inclusion of the Framed-IP-
> > +   Netmask attribute tells the Softwire Concentrator to delegate an
> IPv4
> > +   prefix to the Softwire Initiator (e.g.=2C in the IPv4 over IPv6
> > +   scenarios where the Softwire Initiator is a router=2C see Section
> 3.2.2
> > +   and Section 3.2.4)=2C as the SC should forward packets destined to
> any
> > +   IPv4 address in the prefix to the SI.
> >=20
> >=20
> > Please let me know if this helps with the Framed-IP-Netmask issue.
> >=20
> > Thanks=2C
>=20
>=20
>=20
> Thanks=2C
>=20
> -- Carlos.

--_2d0f8803-c235-44c3-ab8c-a0a23e7d32c3_
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'>
RFC 2865=2C Section 5.9 defines Framed-IP-Netmask:<br><br>
This Attribute indicates the IP netmask to be configured for the
      user when the user is a router to a network.  It MAY be used in
      Access-Accept packets.  It MAY be used in an Access-Request packet
      as a hint by the NAS to the server that it would prefer that
      netmask=2C but the server is not required to honor the hint.
<br><br>In contrast=2C Section 5.22 defines Framed-Route as the mechanism f=
or configuring routing information:<br><br>This Attribute provides routing =
information to be configured for
      the user on the NAS.  It is used in the Access-Accept packet and
      can appear multiple times.
<br><br>Based on this=2C it would appear that Framed-IP-Netmask is intended=
 for configuration of hosts=2C not routers=2C and that Framed-Route is to b=
e used to configure routes. <br><br>Defining two mechanisms for configurati=
on of routes seems like it could create potential interoperability problems=
.&nbsp=3B Since RFC 2865 is a Draft Standard=2C the existing mechanisms are=
 known to be interoperable. <br><br><br>&gt=3B Pasi made a comment regardin=
g the DISCUSS about RFC2865 that says:<br>&gt=3B &gt=3B * RFC 2865=2C by de=
fining new interpretations of the Framed-IP-Address <br>&gt=3B &gt=3B and F=
ramed-IP-Netmask attributes.<br>&gt=3B <br>&gt=3B <br>&gt=3B <br>&gt=3B Wou=
ld adding this text clarify (and remove your concerns with) Section<br>&gt=
=3B &gt=3B 8.2.2?<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B @@ -1551=2C7 +1551=2C1=
4 @@<br>&gt=3B &gt=3B     attributes [RFC2865] may be used by the Softwire =
Concentrator to<br>&gt=3B &gt=3B     delegate an IPv4 prefix to the Softwir=
e Initiator.<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B +   As this practice had be=
en used=2C the inclusion of the Framed-IP-<br>&gt=3B &gt=3B +   Netmask att=
ribute tells the Softwire Concentrator to delegate an<br>&gt=3B IPv4<br>&gt=
=3B &gt=3B +   prefix to the Softwire Initiator (e.g.=2C in the IPv4 over I=
Pv6<br>&gt=3B &gt=3B +   scenarios where the Softwire Initiator is a router=
=2C see Section<br>&gt=3B 3.2.2<br>&gt=3B &gt=3B +   and Section 3.2.4)=2C =
as the SC should forward packets destined to<br>&gt=3B any<br>&gt=3B &gt=3B=
 +   IPv4 address in the prefix to the SI.<br>&gt=3B &gt=3B <br>&gt=3B &gt=
=3B <br>&gt=3B &gt=3B Please let me know if this helps with the Framed-IP-N=
etmask issue.<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B Thanks=2C<br>&gt=3B <br>&g=
t=3B <br>&gt=3B <br>&gt=3B Thanks=2C<br>&gt=3B <br>&gt=3B -- Carlos.<br></b=
ody>
</html>=

--_2d0f8803-c235-44c3-ab8c-a0a23e7d32c3_--

Delivery-date: Mon, 30 Mar 2009 09:32:00 +0000
From: [email-masked]
To: [email-masked]
Cc: [email-masked]
Subject: I-D Action:draft-ietf-radext-extended-attributes-08.txt 
Date: Mon, 30 Mar 2009 02:30:01 -0700 (PDT)

--NextPart

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

	Title           : Extended Remote Authentication Dial In User Service (RADIUS) Attributes
	Author(s)       : Y. Li, et al.
	Filename        : draft-ietf-radext-extended-attributes-08.txt
	Pages           : 13
	Date            : 2009-03-30

For the Remote Authentication Dial In User Service (RADIUS) protocol
to continue to support new applications, the RADIUS attribute type
space must be extended beyond the current limit of 255 possible
attribute types while maintaining backwards compatibility with the
existing protocol.  This document defines a mechanism to accomplish
that task, along with standard methods to group together related
attributes and to encode values that don't fit into 253 octets.

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

Content-Type: text/plain
Content-ID:     <[email-masked]>

--NextPart--

Delivery-date: Sun, 29 Mar 2009 15:45:45 +0000
Cc: Alan DeKok <[email-masked]>, "[email-masked]" <[email-masked]>
From: Klaas Wierenga <[email-masked]>
To: Bernard Aboba <[email-masked]>
Subject: Re: Issue: RADSEC and DTLS docs
Date: Sun, 29 Mar 2009 17:45:20 +0200

--Apple-Mail-35-188798806
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

On Mar 29, 2009, at 5:10 PM, Bernard Aboba wrote:

> > I'll rev the DTLS document soon. We can then see how much of it
> > simply references radsec. If the DTLS-specific portions are small,  
> it
> > may be good to add them to the radsec document.
>
> Even if the DTLS-specific portions are small, there is still a  
> "compliance" issue.
>
> That is, if two vendors say "I implement RADSEC" -- what would it  
> mean, if one could be doing RADIUS over TLS/TCP and another, RADIUS  
> over DTLS/UDP?

ehm.. so they should say "I implement RadSec over TCP" or "I  
implement  RadSec over UDP" ;-)

>
> Whereas if there are two separate documents, and someone says "I  
> implement RADIUS over DTLS",  now we know what transport they are  
> using.
>
> There are similar concerns about RADIUS over TCP, but we discussed  
> indicating in the document that this is only intended for use with  
> RADSEC.

--Apple-Mail-35-188798806
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Mar 29, 2009, =
at 5:10 PM, Bernard Aboba wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div class=3D"hmmessage" =
style=3D"font-size: 10pt; font-family: Verdana; ">&gt; I'll rev the DTLS =
document soon. We can then see how much of it<br>&gt; simply references =
radsec. If the DTLS-specific portions are small, it<br>&gt; may be good =
to add them to the radsec document.<br><br>Even if the DTLS-specific =
portions are small, there is still a "compliance" issue.<span =
class=3D"Apple-converted-space">&nbsp;</span><br><br>That is, if two =
vendors say "I implement RADSEC" -- what would it mean, if one could be =
doing RADIUS over TLS/TCP and another, RADIUS over DTLS/UDP?&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span><br></div></span></blockquote=
><div><br></div>ehm.. so they should say "I implement RadSec over TCP" =
or "I implement &nbsp;RadSec over UDP" ;-)</div><div><br><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div class=3D"hmmessage" =
style=3D"font-size: 10pt; font-family: Verdana; "><br>Whereas if there =
are two separate documents, and someone says "I implement RADIUS over =
DTLS",&nbsp; now we know what transport they are using.<span =
class=3D"Apple-converted-space">&nbsp;</span><br><br>There are similar =
concerns about RADIUS over TCP, but we discussed indicating in the =
document that this is only intended for use with RADSEC.<span =
class=3D"Apple-converted-space">&nbsp;</span><br></div></span></blockquote=
></div><br></body></html>=

--Apple-Mail-35-188798806--

Delivery-date: Sun, 29 Mar 2009 15:12:06 +0000
From: Bernard Aboba <[email-masked]>
To: Alan DeKok <[email-masked]>
CC: "[email-masked]" <[email-masked]>
Subject: RE: Issue: RADSEC and DTLS docs
Date: Sun, 29 Mar 2009 08:10:59 -0700

--_c03cd81f-3d45-4828-b341-7c55e1f4352b_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

>   I'll rev the DTLS document soon.  We can then see how much of it
> simply references radsec.  If the DTLS-specific portions are small=2C it
> may be good to add them to the radsec document.

Even if the DTLS-specific portions are small=2C there is still a "complianc=
e" issue.=20

That is=2C if two vendors say "I implement RADSEC" -- what would it mean=2C=
 if one could be doing RADIUS over TLS/TCP and another=2C RADIUS over DTLS/=
UDP? =20

Whereas if there are two separate documents=2C and someone says "I implemen=
t RADIUS over DTLS"=2C  now we know what transport they are using.=20

There are similar concerns about RADIUS over TCP=2C but we discussed indica=
ting in the document that this is only intended for use with RADSEC.=20

--_c03cd81f-3d45-4828-b341-7c55e1f4352b_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
&gt=3B   I'll rev the DTLS document soon.  We can then see how much of it<b=
r>&gt=3B simply references radsec.  If the DTLS-specific portions are small=
=2C it<br>&gt=3B may be good to add them to the radsec document.<br><br>Eve=
n if the DTLS-specific portions are small=2C there is still a "compliance" =
issue. <br><br>That is=2C if two vendors say "I implement RADSEC" -- what w=
ould it mean=2C if one could be doing RADIUS over TLS/TCP and another=2C RA=
DIUS over DTLS/UDP?&nbsp=3B <br><br>Whereas if there are two separate docum=
ents=2C and someone says "I implement RADIUS over DTLS"=2C&nbsp=3B now we k=
now what transport they are using. <br><br>There are similar concerns about=
 RADIUS over TCP=2C but we discussed indicating in the document that this i=
s only intended for use with RADSEC. <br></body>
</html>=

--_c03cd81f-3d45-4828-b341-7c55e1f4352b_--

Delivery-date: Sat, 28 Mar 2009 15:34:57 +0000
Date: Sat, 28 Mar 2009 08:34:42 -0700
From: Alan DeKok <[email-masked]>
To: "Joseph Salowey (jsalowey)" <[email-masked]>
CC: [email-masked]
Subject: Re: Issue: RADSEC and DTLS docs

Joseph Salowey (jsalowey) wrote:
> Many of the details between RADSEC and DTLS should be the same.  I'm
> worried that the two specs may diverge if the progress differently
> through the IETF.  Is there any reason why we cannot cover DTLS in this
> draft as well?  
> 
> Requested change:
> Have the document cover DTLS.  

  I'll rev the DTLS document soon.  We can then see how much of it
simply references radsec.  If the DTLS-specific portions are small, it
may be good to add them to the radsec document.

  Alan DeKok.

Delivery-date: Sat, 28 Mar 2009 15:30:39 +0000
Date: Sat, 28 Mar 2009 08:29:54 -0700
From: Alan DeKok <[email-masked]>
To: Ignacio Goyret <[email-masked]>
CC: [email-masked]
Subject: Re: radius over tcp

Ignacio Goyret wrote:
> Any thoughts on using SCTP instead of TCP?

  If there's a demand.

> It solves a lot of the problems mentioned for TCP
> and it handles natively the situation of multihomed
> servers (which TCP doesn't).

  People already use traditional RADIUS over IPSec to get better
transport.  I'm not sure that SCTP adds a large benefit here.

  Alan DeKok.

Delivery-date: Fri, 27 Mar 2009 20:57:57 +0000
From: "Hannes Tschofenig" <[email-masked]>
To: <[email-masked]>
Subject: draft-zorn-radius-encattr-15: Obsolete?
Date: Fri, 27 Mar 2009 13:58:52 -0700

Ciao
Hannes

Delivery-date: Fri, 27 Mar 2009 20:52:46 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: Issues update
Date: Fri, 27 Mar 2009 13:52:10 -0700

--_8f001b22-a992-43e1-b917-e1c02eb625bb_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

In order to update the status of existing documents=2C we are requesting th=
at editors send a summary to the list of what they believe is the status of=
 open issues on their documents.  We would then request that the issue file=
rs confirm the status of the issues=2C so that we can get an accurate statu=
s on them.=20

 EMAILING FOR SOMETHING OR OTHER
Join m=

--_8f001b22-a992-43e1-b917-e1c02eb625bb_
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'>
In order to update the status of existing documents=2C we are requesting th=
at editors send a summary to the list of what they believe is the status of=
 open issues on their documents.&nbsp=3B We would then request that the iss=
ue filers confirm the status of the issues=2C so that we can get an accurat=
e status on them. <br><br><table style=3D"border-top: 1px solid black=3B fo=
nt-weight: bold=3B font-family: 'Segoe UI'=2CTahoma=2Csan-serif=3B"><tbody>=
<tr><td><a href=3D"http://im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_=
GreaterGood" style=3D"font-size: 9pt=3B color: rgb(1=2C 132=2C 203)=3B text=
-decoration: none=3B"><img style=3D"border-style: none=3B" src=3D"http://gf=
x1.hotmail.com/mail/w3/ltr/i_charity.gif" alt=3D"i'm"> EMAILING FOR SOMETHI=
NG OR OTHER<br><span style=3D"padding: 0px 24px=3B font-size: 8pt=3B color:=
 rgb(63=2C 181=2C 85)=3B text-decoration: underline=3B">Join m</span></a></=
td></tr></tbody></table></body>
</html>=

--_8f001b22-a992-43e1-b917-e1c02eb625bb_--

Delivery-date: Fri, 27 Mar 2009 18:20:21 +0000
From: "David B. Nelson" <[email-masked]>
To: <[email-masked]>
Subject: RE: IETF 74 RADEXT WG Meeting Agenda and Meeting materials
Date: Fri, 27 Mar 2009 14:19:38 -0400
Organization: Elbrys Networks, Inc.

David Mitton writes...

> The audio stream was up, but it seems to have flaked out
> on me several times.

Yeah.  I guess on one level it's amazing that it works at all, given the
potential scaling issues of providing that kind of service.  On another
level, it's really not all that useful for remote participation if it works
only part of the time, or the latency becomes such that questions about
what's being said asked via jabber arrive partway into the *next*
presentation.

Delivery-date: Fri, 27 Mar 2009 17:31:41 +0000
Date: Fri, 27 Mar 2009 10:30:54 -0700
To: Alan DeKok <[email-masked]>
From: Ignacio Goyret <[email-masked]>
Subject: radius over tcp
Cc: [email-masked]

Any thoughts on using SCTP instead of TCP?

It solves a lot of the problems mentioned for TCP
and it handles natively the situation of multihomed
servers (which TCP doesn't).

-Ignacio

Delivery-date: Fri, 27 Mar 2009 17:20:55 +0000
Date: Fri, 27 Mar 2009 17:20:11 +0000 (GMT)
From: David Mitton <[email-masked]>
Reply-To: [email-masked]
To: [email-masked]
Cc: [email-masked], [email-masked]
Subject: Re: RE: IETF 74 RADEXT WG Meeting Agenda and Meeting materials

<html><HEAD><LINK media=3Dall href=3D"static/deg/css/wysiwyg.css" type=3Dte=
xt/css rel=3Dstylesheet>
<META content=3D"MSHTML 6.00.6000.16809" name=3DGENERATOR></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<P>The audio stream was up, but it seems to have flaked out on me several t=
imes.</P>
<P>It's back up now...</P>
<P>Unfortunately I'm not able to jabber today.</P>
<P>Dave.<BR><BR><BR>Mar 27, 2009 10:49:54 AM, [email-masked] wr=
ote:<BR></P>
<BLOCKQUOTE style=3D"BORDER-LEFT: rgb(102,153,204) 3px solid">
<STYLE>
<!--
 /* Font Definitions */
 @font-face
=09{font-family:Verdana;
=09panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
=09{margin:0in;
=09margin-bottom:.0001pt;
=09font-size:12.0pt;
=09font-family:"Times New Roman";}
a:link, span.MsoHyperlink
=09{color:blue;
=09text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
=09{color:purple;
=09text-decoration:underline;}
p
=09{mso-margin-top-alt:auto;
=09margin-right:0in;
=09mso-margin-bottom-alt:auto;
=09margin-left:0in;
=09font-size:12.0pt;
=09font-family:"Times New Roman";}
span.EmailStyle18
=09{mso-style-type:personal-reply;
=09font-family:Arial;
=09color:navy;}
@page Section1
=09{size:8.5in 11.0in;
=09margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
=09{page:Section1;}
-->

</STYLE>

<DIV class=3DSection1>
<DIV style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: me=
dium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt =
solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3DVerdana siz=
e=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Verdana">As usual, we wi=
ll be utilizing jabber and streaming audio for remote participants.<FONT co=
lor=3Dnavy><SPAN style=3D"COLOR: navy"><?xml:namespace prefix =3D o ns =3D =
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></FONT></SPAN=
></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3DArial color=
=3Dnavy size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">The jabber room is up, but the streaming audio service currently yie=
lds a =E2=80=9Cfile not found=E2=80=9D error. &nbsp;I hope this will be rem=
edied prior to the 9 AM PDT session start time.<o:p></o:p></SPAN></FONT></P=
></DIV></DIV></BLOCKQUOTE></BODY></html>

Delivery-date: Fri, 27 Mar 2009 14:46:39 +0000
From: "David B. Nelson" <[email-masked]>
To: "'Bernard Aboba'" <[email-masked]>, <[email-masked]>
Subject: RE: IETF 74 RADEXT WG Meeting Agenda and Meeting materials
Date: Fri, 27 Mar 2009 10:46:04 -0400
Organization: Elbrys Networks, Inc.

This is a multi-part message in MIME format.

------=_NextPart_000_03AD_01C9AEC9.3A563EC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

As usual, we will be utilizing jabber and streaming audio for remote
participants.

The jabber room is up, but the streaming audio service currently yields a
"file not found" error.  I hope this will be remedied prior to the 9 AM PDT
session start time.

------=_NextPart_000_03AD_01C9AEC9.3A563EC0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
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 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

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

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana'>As usual, we will be =
utilizing
jabber and streaming audio for remote participants.<font =
color=3Dnavy><span
style=3D'color:navy'><o:p></o:p></span></font></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>The
jabber room is up, but the streaming audio service currently yields a =
&#8220;file
not found&#8221; error. &nbsp;I hope this will be remedied prior to the =
9 AM PDT
session start time.<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_03AD_01C9AEC9.3A563EC0--

Delivery-date: Fri, 27 Mar 2009 13:25:19 +0000
From: Bernard Aboba <[email-masked]>
To: <[email-masked]>, <[email-masked]>
CC: "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>, <[email-masked]>, <[email-masked]>, "[email-masked]" <[email-masked]>
Subject: RE: DISCUSS: draft-ietf-softwire-hs-framework-l2tpv2
Date: Fri, 27 Mar 2009 06:24:19 -0700

--_ec8acea2-123d-434b-ad56-c3f541402036_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am not sure that the absence/presence of NAS-IP-Address/NAS-IPv6-Address =
necessarily provides information about the nature of the traffic within RAD=
IUS accounting. For example=2C it is quite possible that both attributes wi=
ll be present.=20

Is there a reason why we can't just define accounting attributes to provide=
 the information you're looking for?

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> CC: [email-masked]=3B [email-masked]=3B [email-masked]=3B s=
[email-masked]=3B draft-ietf-softwire-hs-framework-l2tpv2@to=
ols.ietf.org
> From: [email-masked]
> To: [email-masked]
> Subject: Re: DISCUSS: draft-ietf-softwire-hs-framework-l2tpv2=20
> Date: Fri=2C 27 Mar 2009 09:39:31 +0100
>=20
> Hi all=2C
>=20
> Just an update on one item:
>=20
> [snip]
> >
> >> * RFC 2866=2C by referencing draft-stevant-softwire-accounting=2C whic=
h
> >> redefines the format of the NAS-IP-Address attribute (which only
> >> supports IPv4 addresses=3B NAS-IPv6-Address is used to contain IPv6
> >> addresses).
> >
> > It looks like draft-stevant-... indeed has text that isn't correct
> > (but also looks easy to fix). But this is an informative reference (to
> > an expired internet-draft)=2C so it probably should not block the
> > publication of this document.
>=20
>=20
> I updated draft-stevant-softwire-accounting and fixed the issue about =20
> attributes. The document is not yet published (the datatracker tool is =20
> hanging when uploading ...) but here is an excerpt of the paragraph =20
> you referenced in this draft:
>=20
> 4.2.  Differentiation based on context
>=20
>     A RADIUS accounting entry=2C as defined in [RFC2867] and updated by
>     [RFC3162]=2C also includes the NAS-IP-Address and NAS-IPv6-Address
>     attributes=2C which gives the IP address of the NAS used as the
>     softwire endpoint.  Based on this information=2C an operator can =20
> decide
>     if this softwire is based on IPv4 or IPv6.  In the case of provider
>     only deploying IPv6 over IPv4 and IPv4 over IPv6 softwires=2C the
>     nature of the traffic reported in the accounting information depends
>     of which attribute between NAS-IP-Address and NAS-IPv6-Address is
>     set.  If NAS-IP-Address is set in the accounting entry=2C accounted
>     traffic is IPv6.  If NAS-IPv6-Address is set in the accounting =20
> entry=2C
>     accounted traffic is IPv4.  However=2C this solution requires extra
>     checking when building accounting report and obviously does not work
>     in case of IPvX over IPvX softwires.

--_ec8acea2-123d-434b-ad56-c3f541402036_
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'>
I am not sure that the absence/presence of NAS-IP-Address/NAS-IPv6-Address =
necessarily provides information about the nature of the traffic within RAD=
IUS accounting. For example=2C it is quite possible that both attributes wi=
ll be present. <br><br>Is there a reason why we can't just define accountin=
g attributes to provide the information you're looking for?<br><br>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>&gt=3B CC: [email-masked]=3B [email-masked]=3B Bernard_Abob=
[email-masked]=3B [email-masked]=3B draft-ietf-softwire-hs-f=
[email-masked]<br>&gt=3B From: bruno.stevant@telecom-bretag=
ne.eu<br>&gt=3B To: [email-masked]<br>&gt=3B Subject: Re: DISCUSS: d=
raft-ietf-softwire-hs-framework-l2tpv2 <br>&gt=3B Date: Fri=2C 27 Mar 2009 =
09:39:31 +0100<br>&gt=3B <br>&gt=3B Hi all=2C<br>&gt=3B <br>&gt=3B Just an =
update on one item:<br>&gt=3B <br>&gt=3B [snip]<br>&gt=3B &gt=3B<br>&gt=3B =
&gt=3B&gt=3B * RFC 2866=2C by referencing draft-stevant-softwire-accounting=
=2C which<br>&gt=3B &gt=3B&gt=3B redefines the format of the NAS-IP-Address=
 attribute (which only<br>&gt=3B &gt=3B&gt=3B supports IPv4 addresses=3B NA=
S-IPv6-Address is used to contain IPv6<br>&gt=3B &gt=3B&gt=3B addresses).<b=
r>&gt=3B &gt=3B<br>&gt=3B &gt=3B It looks like draft-stevant-... indeed has=
 text that isn't correct<br>&gt=3B &gt=3B (but also looks easy to fix). But=
 this is an informative reference (to<br>&gt=3B &gt=3B an expired internet-=
draft)=2C so it probably should not block the<br>&gt=3B &gt=3B publication =
of this document.<br>&gt=3B <br>&gt=3B <br>&gt=3B I updated draft-stevant-s=
oftwire-accounting and fixed the issue about  <br>&gt=3B attributes. The do=
cument is not yet published (the datatracker tool is  <br>&gt=3B hanging wh=
en uploading ...) but here is an excerpt of the paragraph  <br>&gt=3B you r=
eferenced in this draft:<br>&gt=3B <br>&gt=3B 4.2.  Differentiation based o=
n context<br>&gt=3B <br>&gt=3B     A RADIUS accounting entry=2C as defined =
in [RFC2867] and updated by<br>&gt=3B     [RFC3162]=2C also includes the NA=
S-IP-Address and NAS-IPv6-Address<br>&gt=3B     attributes=2C which gives t=
he IP address of the NAS used as the<br>&gt=3B     softwire endpoint.  Base=
d on this information=2C an operator can  <br>&gt=3B decide<br>&gt=3B     i=
f this softwire is based on IPv4 or IPv6.  In the case of provider<br>&gt=
=3B     only deploying IPv6 over IPv4 and IPv4 over IPv6 softwires=2C the<b=
r>&gt=3B     nature of the traffic reported in the accounting information d=
epends<br>&gt=3B     of which attribute between NAS-IP-Address and NAS-IPv6=
-Address is<br>&gt=3B     set.  If NAS-IP-Address is set in the accounting =
entry=2C accounted<br>&gt=3B     traffic is IPv6.  If NAS-IPv6-Address is s=
et in the accounting  <br>&gt=3B entry=2C<br>&gt=3B     accounted traffic i=
s IPv4.  However=2C this solution requires extra<br>&gt=3B     checking whe=
n building accounting report and obviously does not work<br>&gt=3B     in c=
ase of IPvX over IPvX softwires.<br><br></body>
</html>=

--_ec8acea2-123d-434b-ad56-c3f541402036_--

Delivery-date: Thu, 26 Mar 2009 20:40:33 +0000
Date: Thu, 26 Mar 2009 20:38:20 +0100
From: Stefan Winter <[email-masked]>
To: "Joseph Salowey (jsalowey)" <[email-masked]>
CC: [email-masked]
Subject: Re: Issue: RADSEC and DTLS docs

Hi,

> Have the document cover DTLS.  
>   

I suggest we discuss this in the radext meeting and see how we go from 
there.

Greetings,

Stefan Winter

Delivery-date: Thu, 26 Mar 2009 20:39:47 +0000
Date: Thu, 26 Mar 2009 20:37:04 +0100
From: Stefan Winter <[email-masked]>
To: "Joseph Salowey (jsalowey)" <[email-masked]>
CC: [email-masked]
Subject: Re: Issue: NAS identity

Hi,

> Discuss in the document that the NAS can be identified by something
> other than source IP address.  
>   

Sure, that's possible. FOr X.509 cert operation, I guess this is a 
non-issue, since there are numerous ways to identify a peer without 
using its IP address.
For PSK, the PSK Identifier Field can be used to identify the peer. This 
can be used to create arbitrary identifiers, independent of the IP 
address of the NAS.

This works both ways: if one has configured many tuples of (IP,sh-sec), 
it might be desirable to keep that configuration - in which case the 
Identifier field can be set to the IP address.

In none of these cases it is necessary to use layer 3 packet inspection 
to identify the peer - the Identifier field is always sufficient. Is 
that what you menat? Then I'll update the text accordingly.

Greetings,

Stefan Winter

Delivery-date: Thu, 26 Mar 2009 18:41:15 +0000
Content-class: urn:content-classes:message
Subject: Issue: NAS identity
Date: Thu, 26 Mar 2009 11:40:29 -0700
From: "Joseph Salowey (jsalowey)" <[email-masked]>
To: <[email-masked]>

Description of issue
Submitter name: Joseph Salowey
Submitter email address: [email-masked]
Date first submitted: 3/26/2009
Reference: URL to e-mail describing problem, if available
Document: draft-ietf-radext-radsec-04.txt
Comment type: T
Priority: S
Section:=20
Rationale/Explanation of issue:
Current RADIUS specs the NAS identity is tightly coupled with IP address
because this is how the shared secret is referenced.  With new modes of
authentication it seems that the  identity need not be tied to IP
address anymore.   This could help with dynamic addressing and NATS. =20

Requested change:
Discuss in the document that the NAS can be identified by something
other than source IP address. =20

Delivery-date: Thu, 26 Mar 2009 18:34:21 +0000
Content-class: urn:content-classes:message
Subject: Issue: RADSEC and DTLS docs
Date: Thu, 26 Mar 2009 11:33:45 -0700
From: "Joseph Salowey (jsalowey)" <[email-masked]>
To: <[email-masked]>

Submitter name: Joe Salowey
Submitter email address: [email-masked]
Date first submitted: 3/26/2009
Document: draft-ietf-radext-radsec-04.txt
Comment type: T
Priority: 1
Section:=20
Rationale/Explanation of issue:
Many of the details between RADSEC and DTLS should be the same.  I'm
worried that the two specs may diverge if the progress differently
through the IETF.  Is there any reason why we cannot cover DTLS in this
draft as well? =20

Requested change:
Have the document cover DTLS. =20

Delivery-date: Thu, 26 Mar 2009 18:29:38 +0000
Content-class: urn:content-classes:message
Subject: Issue RADSEC certificate handling
Date: Thu, 26 Mar 2009 11:29:16 -0700
From: "Joseph Salowey (jsalowey)" <[email-masked]>
To: <[email-masked]>

Description of issue
Submitter name: Joe Salowey
Submitter email address: [email-masked]
Date first submitted:=20
Reference:=20
Document: draft-ietf-radext-radsec-04.txt=20
Comment type: T
Priority: S
Section: 2.2
Rationale/Explanation of issue:

This connection setup and certificate handling section is improved, but
I think it could still use some work. =20

Requested change:

1. The discussion of TLS cipher suites is broken apart into several
places in the document, some of them normative and some of them
informative.  I believe the normative and informative information is
reversed.  The implementation requirements for supported cipher suites
should go in this section.

2. When is it acceptable not to validate the SRV entry in the
certificate?=20

3. The section should state that matching should be done against locally
configured names (as opposed to information retrieved from DNS).=20

4. Is there any particular URI type that would be useful for RADIUS?=20

Delivery-date: Thu, 26 Mar 2009 18:12:37 +0000
From: "Glen Zorn" <[email-masked]>
To: "'Bernard Aboba'" <[email-masked]>
Cc: <[email-masked]>
Subject: RE: REMINDER:  Call for Adoption of "RADIUS attributes for IPv6 Access Networks" as a RADEXT WG work item
Date: Thu, 26 Mar 2009 11:11:02 -0700

This is a multipart message in MIME format.

------=_NextPart_000_018E_01C9AE03.93E0ADC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

OK w/me, though I might note that a) this is a poor time for a WGLC (since
lots of WG members are likely quite busy right now) & b) the draft has
changed recently.

From: [email-masked] [mailto:[email-masked]] On
Behalf Of Bernard Aboba
Sent: Thursday, March 26, 2009 10:13 AM
To: [email-masked]
Subject: REMINDER: Call for Adoption of "RADIUS attributes for IPv6 Access
Networks" as a RADEXT WG work item

This is a reminder of an ongoing call for review of the document "RADIUS
attributes for IPv6 Access Networks" for adoption as a RADEXT WG work item.
This document was discussed at IETF 73, and is being targeted at Proposed
Standard status. 
 
The document is available for review here:
 <http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access>
http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access

This call for review will last until March 30, 2009.  Please send email to
the RADEXT WG mailing list indicating whether you support adoption of this
document as a RADEXT WG work item.  If you have comments on the document,
please also send these to the list in the format described on the RADEXT WG
Issues list:
 <http://www.drizzle.com/%7Eaboba/RADEXT/>
http://www.drizzle.com/~aboba/RADEXT/

------=_NextPart_000_018E_01C9AE03.93E0ADC0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Arial =
Black","sans-serif";
color:#7030A0'>OK w/me, though I might note that a) this is a poor time =
for a
WGLC (since lots of WG members are likely quite busy right now) &amp; b) =
the
draft has changed recently.<o:p></o:p></span></p>

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

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

<div>

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

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
[email-masked]
[mailto:[email-masked]] <b>On Behalf Of </b>Bernard =
Aboba<br>
<b>Sent:</b> Thursday, March 26, 2009 10:13 AM<br>
<b>To:</b> [email-masked]<br>
<b>Subject:</b> REMINDER: Call for Adoption of &quot;RADIUS attributes =
for IPv6
Access Networks&quot; as a RADEXT WG work item<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'>This is a reminder of an ongoing =
call for
review of the document &quot;RADIUS attributes for IPv6 Access =
Networks&quot;
for adoption as a RADEXT WG work item.&nbsp; This document =
was&nbsp;discussed
at IETF 73, and is being targeted at Proposed Standard status. <br>
&nbsp;<br>
The document is available for review here:<br>
<span style=3D'color:#0068CF'><a
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access"><s=
pan
style=3D'color:#0066CC'>http://tools.ietf.org/html/draft-lourdelet-radext=
-ipv6-access</span></a></span><br>
<br>
This call for review will last until March 30, 2009.&nbsp; Please send =
email to
the RADEXT WG mailing list indicating whether you support adoption of =
this
document as a RADEXT WG work item.&nbsp; If you have comments on the =
document,
please also send these to the list in the format described on the RADEXT =
WG
Issues list:<br>
<a href=3D"http://www.drizzle.com/%7Eaboba/RADEXT/" =
target=3D"_blank"><span
style=3D'color:#0068CF'>http://www.drizzle.com/~aboba/RADEXT/</span></a><=
br>
<br>
<o:p></o:p></span></p>

<table class=3DMsoNormalTable border=3D1 cellpadding=3D0 =
style=3D'border:none;
 border-top:solid black 1.0pt'>
 <tr>
  <td style=3D'border:none;padding:.75pt .75pt .75pt .75pt'></td>
 </tr>
</table>

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

</div>

</div>

</body>

</html>

------=_NextPart_000_018E_01C9AE03.93E0ADC0--

Delivery-date: Thu, 26 Mar 2009 17:13:30 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: REMINDER:  Call for Adoption of "RADIUS attributes for IPv6 Access Networks" as a RADEXT WG work item
Date: Thu, 26 Mar 2009 10:13:07 -0700

--_c9e0c8c2-bf4c-4e62-9976-24af3718a713_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is a reminder of an ongoing call for review of the document "RADIUS at=
tributes for IPv6
Access Networks" for adoption as a RADEXT WG work item.  This document
was discussed at IETF 73=2C and is being targeted at Proposed Standard
status.=20

=20
The document is available for review here:
http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access

This
call for review will last until March 30=2C 2009.  Please send email to
the RADEXT WG mailing list indicating whether you support adoption of
this document as a RADEXT WG work item.  If you have comments on the
document=2C please also send these to the list in the format described on
the RADEXT WG Issues list:
http://www.drizzle.com/~aboba/RADEXT/

--_c9e0c8c2-bf4c-4e62-9976-24af3718a713_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
This is a reminder of an ongoing call for review of the document "RADIUS at=
tributes for IPv6
Access Networks" for adoption as a RADEXT WG work item.&nbsp=3B This docume=
nt
was&nbsp=3Bdiscussed at IETF 73=2C and is being targeted at Proposed Standa=
rd
status. <br>
&nbsp=3B<br>The document is available for review here:<br><span style=3D"fo=
nt-size: 10pt=3B color: rgb(0=2C 104=2C 207)=3B font-family: 'Verdana'=2C's=
ans-serif'=3B"><a href=3D"http://tools.ietf.org/html/draft-lourdelet-radext=
-ipv6-access" rel=3D"nofollow"><font color=3D"#0066cc">http://tools.ietf.or=
g/html/draft-lourdelet-radext-ipv6-access</font></a></span><br><br>This
call for review will last until March 30=2C 2009.&nbsp=3B Please send email=
 to
the RADEXT WG mailing list indicating whether you support adoption of
this document as a RADEXT WG work item.&nbsp=3B If you have comments on the
document=2C please also send these to the list in the format described on
the RADEXT WG Issues list:<br><a rel=3D"nofollow" href=3D"http://www.drizzl=
e.com/%7Eaboba/RADEXT/" target=3D"_blank"><font color=3D"#0068cf">http://ww=
w.drizzle.com/~aboba/RADEXT/</font></a><br><br><br><table style=3D"border-t=
op: 1px solid black=3B font-weight: bold=3B font-family: 'Segoe UI'=2CTahom=
a=2Csan-serif=3B"><tbody><tr><td><br></td></tr></tbody></table></body>
</html>=

--_c9e0c8c2-bf4c-4e62-9976-24af3718a713_--

Delivery-date: Thu, 26 Mar 2009 17:08:14 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: REMINDER: Slides for IETF 74 RADEXT WG meeting
Date: Thu, 26 Mar 2009 10:07:27 -0700

--_d1f5fcda-0193-49f6-a9aa-dd1131d727e6_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

If you're presenting at the IETF 74 RADEXT WG meeting tomorrow=2C you need =
to start preparing your slides NOW=2C and email them to myself and/or Dave =
by 5 PM PDT today.  =20

--_d1f5fcda-0193-49f6-a9aa-dd1131d727e6_
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'>
If you're presenting at the IETF 74 RADEXT WG meeting tomorrow=2C you need =
to start preparing your slides NOW=2C and email them to myself and/or Dave =
by 5 PM PDT today.&nbsp=3B&nbsp=3B <br><br><br><br><table style=3D"border-t=
op: 1px solid black=3B font-weight: bold=3B font-family: 'Segoe UI'=2CTahom=
a=2Csan-serif=3B"><tbody><tr><td><a href=3D"http://im.live.com/Messenger/IM=
/Home/?source=3DEML_WLHM_GreaterGood" style=3D"font-size: 9pt=3B color: rgb=
(1=2C 132=2C 203)=3B text-decoration: none=3B"><span style=3D"padding: 0px =
24px=3B font-size: 8pt=3B color: rgb(63=2C 181=2C 85)=3B text-decoration: u=
nderline=3B"><br></span></a></td></tr></tbody></table></body>
</html>=

--_d1f5fcda-0193-49f6-a9aa-dd1131d727e6_--

Delivery-date: Thu, 26 Mar 2009 01:19:42 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: IETF 74 RADEXT WG Meeting Agenda and Meeting materials
Date: Wed, 25 Mar 2009 18:19:14 -0700

--_6edd1ee5-4a7a-45cc-9d55-207cf3a3b580_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

As usual=2C the agenda for the IETF 74 meeting is available here:
http://tools.ietf.org/agenda/74/

The agenda for the IETF 74 RADEXT WG meeting is available here:
http://www.ietf.org/proceedings/09mar/agenda/radext.txt

The slides are available here:
https://datatracker.ietf.org/meeting/74/materials.html

As usual=2C we will be utilizing jabber and streaming audio for remote part=
icipants.  If you have a specific remote participation request (e.g. a conf=
erence bridge)=2C let us know.=20

--_6edd1ee5-4a7a-45cc-9d55-207cf3a3b580_
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'>
As usual=2C the agenda for the IETF 74 meeting is available here:<br>http:/=
/tools.ietf.org/agenda/74/<br><br>The agenda for the IETF 74 RADEXT WG meet=
ing is available here:<br>http://www.ietf.org/proceedings/09mar/agenda/rade=
xt.txt<br><br>The slides are available here:<br>https://datatracker.ietf.or=
g/meeting/74/materials.html<br><br>As usual=2C we will be utilizing jabber =
and streaming audio for remote participants.&nbsp=3B If you have a specific=
 remote participation request (e.g. a conference bridge)=2C let us know. <b=
r><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><tabl=
e style=3D"border-top: 1px solid black=3B font-weight: bold=3B font-family:=
 'Segoe UI'=2CTahoma=2Csan-serif=3B"><tbody><tr><td><br></td></tr></tbody><=
/table></body>
</html>=

--_6edd1ee5-4a7a-45cc-9d55-207cf3a3b580_--

Delivery-date: Thu, 26 Mar 2009 00:39:02 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: Slides for IETF 74 RADEXT WG meeting
Date: Wed, 25 Mar 2009 17:38:51 -0700

--_74323b55-e183-467e-bf57-e946c2476ae7_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The RADEXT WG is scheduled to meet on Friday=2C March 27=2C 2009 from 9:00 =
- 11:30 AM.=20

=20

If you are scheduled to present=2C please email slides to myself and/or Dav=
e Nelson ASAP.=20

 EMAILING FOR MODERATE MEDIOCRITY
Join me=

--_74323b55-e183-467e-bf57-e946c2476ae7_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
The RADEXT WG is scheduled to meet on Friday=2C March 27=2C 2009&nbsp=3Bfro=
m 9:00 - 11:30 AM. <br>
&nbsp=3B<br>
If you are scheduled to present=2C please email slides to myself and/or Dav=
e Nelson ASAP. <br><br><table style=3D"border-top: 1px solid black=3B font-=
weight: bold=3B font-family: 'Segoe UI'=2CTahoma=2Csan-serif=3B"><tbody><tr=
><td><a href=3D"http://im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_Gre=
aterGood" style=3D"font-size: 9pt=3B color: rgb(1=2C 132=2C 203)=3B text-de=
coration: none=3B"><img style=3D"border-style: none=3B" src=3D"http://gfx1.=
hotmail.com/mail/w3/ltr/i_charity.gif" alt=3D"i'm"> EMAILING FOR MODERATE M=
EDIOCRITY<br><span style=3D"padding: 0px 24px=3B font-size: 8pt=3B color: r=
gb(63=2C 181=2C 85)=3B text-decoration: underline=3B">Join me</span></a></t=
d></tr></tbody></table></body>
</html>=

--_74323b55-e183-467e-bf57-e946c2476ae7_--

Delivery-date: Thu, 26 Mar 2009 00:38:14 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: REMINDER: RADEXT WG Last Call on the RADSEC specification
Date: Wed, 25 Mar 2009 17:37:22 -0700

--_cd3b4f4d-d3e9-41a5-8515-12b1a57fbecd_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is a reminder of the ongoing RADEXT WG last call on the RADSEC
specification=2C prior to sending this document on to the IESG for
publication as an Experimental RFC.  The document is available for
inspection here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-04.txt

RADEXT WG last call will last until March 30=2C 2009.  Please send
comments to the RADEXT WG mailing list using the format described in
the RADEXT Issues list (http://www.drizzle.com/~aboba/RADEXT/).=20

 EMAILING FOR THE LESSER BAD
Join me=

--_cd3b4f4d-d3e9-41a5-8515-12b1a57fbecd_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
This is a reminder of the ongoing RADEXT WG last call on the RADSEC
specification=2C prior to sending this document on to the IESG for
publication as an Experimental RFC.&nbsp=3B The document is available for
inspection here:<br><a rel=3D"nofollow" href=3D"http://www.ietf.org/interne=
t-drafts/draft-ietf-radext-radsec-04.txt">http://www.ietf.org/internet-draf=
ts/draft-ietf-radext-radsec-04.txt</a><br>
<br>RADEXT WG last call will last until March 30=2C 2009.&nbsp=3B Please se=
nd
comments to the RADEXT WG mailing list using the format described in
the RADEXT Issues list (http://www.drizzle.com/~aboba/RADEXT/). <br><br><br=
><table style=3D"border-top: 1px solid black=3B font-weight: bold=3B font-f=
amily: 'Segoe UI'=2CTahoma=2Csan-serif=3B"><tbody><tr><td><a href=3D"http:/=
/im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_GreaterGood" style=3D"fon=
t-size: 9pt=3B color: rgb(1=2C 132=2C 203)=3B text-decoration: none=3B"><im=
g style=3D"border-style: none=3B" src=3D"http://gfx1.hotmail.com/mail/w3/lt=
r/i_charity.gif" alt=3D"i'm"> EMAILING FOR THE LESSER BAD<br><span style=3D=
"padding: 0px 24px=3B font-size: 8pt=3B color: rgb(63=2C 181=2C 85)=3B text=
-decoration: underline=3B">Join me</span></a></td></tr></tbody></table></bo=
dy>
</html>=

--_cd3b4f4d-d3e9-41a5-8515-12b1a57fbecd_--

Delivery-date: Mon, 23 Mar 2009 17:16:06 +0000
Date: Mon, 23 Mar 2009 18:15:15 +0100
From: [email-masked]
To: [email-masked]
Subject: Re: Call for Adoption of "NAI-based Peer Discovery" as a RADEXT WG work item

> This is a call for review of the document "NAI-based Peer Discovery"  
> for adoption as a RADEXT WG work item.  This document was formerly  
> part of the RADSEC document, and is now being split off into its own  
> document, which (like RADSEC) will be targeted toward Experimental  
> Status.

I support the adoption.

Stefan Winter

Delivery-date: Tue, 17 Mar 2009 13:20:09 +0000
From: "Dave Nelson" <[email-masked]>
To: "'Abhishek Tiwari'" <[email-masked]>
Cc: <[email-masked]>
Subject: RE: Review of draft-tiwari-radext-tunnel-type-02.txt
Date: Tue, 17 Mar 2009 09:19:32 -0400

Abhishek Tiwari writes...

> Can you please let me know the latest status on this document?

The status of this draft will be discussed during the RADEXT WG session at
IETF 74.  It has been assigned a five minute slot.  We'll summarize any
comments from WGLC. After that, assuming no issues, we'll send it off to the
IESG for their review. 

Delivery-date: Tue, 17 Mar 2009 10:58:45 +0000
From: Abhishek Tiwari <[email-masked]>
To: "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>
Date: Tue, 17 Mar 2009 18:57:48 +0800
Subject: Review of draft-tiwari-radext-tunnel-type-02.txt
Accept-Language: en-US
acceptlanguage: en-US

--_000_701A6382E4B1B0458FC27DE8F6A477081E80B715D9AAEXMSGC424so_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi David,

Can you please let me know the latest status on this document? WG last call=
 completed on December 15th, 2008 but nothing has changed since then. Let m=
e know if you need some information from my side.

Thanks,
Abhishek

-----Original Message-----

From: [email-masked] [mailto:[email-masked]] On=
 Behalf Of David B. Nelson

Sent: Tuesday, September 09, 2008 10:52 PM

To: [email-masked]

Subject: Review of draft-tiwari-radext-tunnel-type-02.txt

This is call for the RADEXT WG to review the I-D

draft-tiwari-radext-tunnel-type-02.txt, which assigns new values of the

RADIUS Tunnel-Type Attribute.

After a discussion among the draft author, our esteemed Area Director and

the WG Co-Chairs, it was decided that review of this document in RADEXT was

appropriate and that, if the WG concurred, we would make it a WG item and

forward it to the IESG to determine IETF Consensus.

This document is now in RADEXT WG Pre-WG Review.

Please review this very short (5 pages) draft located at:

http://www.ietf.org/internet-drafts/draft-tiwari-radext-tunnel-type-02.txt

Please send a message to the RADEXT list indicating:

(1) Should this document be taken on as RADEXT WG work item?

(2) Are the technical or editorial issues with this document?

The comment period will last until October 5, 2008.

Regards,

Dave

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

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
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;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<div style=3D'mso-element:para-border-div;border:none;border-bottom:double =
windowtext 2.25pt;
padding:0in 0in 1.0pt 0in'>

<p class=3DMsoNormal style=3D'border:none;padding:0in'>Hi David,<o:p></o:p>=
</p>

<p class=3DMsoNormal style=3D'border:none;padding:0in'><o:p>&nbsp;</o:p></p=

<p class=3DMsoNormal style=3D'border:none;padding:0in'>Can you please let m=
e know
the latest status on this document? WG last call completed on December 15<s=
up>th</sup>,
2008 but nothing has changed since then. Let me know if you need some
information from my side.<o:p></o:p></p>

<p class=3DMsoNormal style=3D'border:none;padding:0in'><o:p>&nbsp;</o:p></p=

<p class=3DMsoNormal style=3D'border:none;padding:0in'>Thanks,<o:p></o:p></=
p>

<p class=3DMsoNormal style=3D'border:none;padding:0in'>Abhishek<o:p></o:p><=
/p>

<p class=3DMsoNormal style=3D'border:none;padding:0in'><o:p>&nbsp;</o:p></p=

</div>

<pre>-----Original Message-----<o:p></o:p></pre><pre>From: owner-radiusext@=
ops.ietf.org [<a
href=3D"mailto:[email-masked]">mailto:[email-masked]=
f.org</a>] On Behalf Of David B. Nelson<o:p></o:p></pre><pre>Sent: Tuesday,=
 September 09, 2008 10:52 PM<o:p></o:p></pre><pre>To: [email-masked]=
g<o:p></o:p></pre><pre>Subject: Review of draft-tiwari-radext-tunnel-type-0=
2.txt<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>This is call for the=
 RADEXT WG to review the I-D<o:p></o:p></pre><pre>draft-tiwari-radext-tunne=
l-type-02.txt, which assigns new values of the<o:p></o:p></pre><pre>RADIUS =
Tunnel-Type Attribute.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Aft=
er a discussion among the draft author, our esteemed Area Director and<o:p>=
</o:p></pre><pre>the WG Co-Chairs, it was decided that review of this docum=
ent in RADEXT was<o:p></o:p></pre><pre>appropriate and that, if the WG conc=
urred, we would make it a WG item and<o:p></o:p></pre><pre>forward it to th=
e IESG to determine IETF Consensus.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p><=
/pre><pre>This document is now in RADEXT WG Pre-WG Review.<o:p></o:p></pre>=
<pre><o:p>&nbsp;</o:p></pre><pre>Please review this very short (5 pages) dr=
aft located at:<o:p></o:p></pre><pre><a
href=3D"http://www.ietf.org/internet-drafts/draft-tiwari-radext-tunnel-type=
-02.txt">http://www.ietf.org/internet-drafts/draft-tiwari-radext-tunnel-typ=
e-02.txt</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Please send a=
 message to the RADEXT list indicating:<o:p></o:p></pre><pre><o:p>&nbsp;</o=
:p></pre><pre>(1) Should this document be taken on as RADEXT WG work item?<=
o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>(2) Are the technical or e=
ditorial issues with this document?<o:p></o:p></pre><pre><o:p>&nbsp;</o:p><=
/pre><pre>The comment period will last until October 5, 2008.<o:p></o:p></p=
re><pre><o:p>&nbsp;</o:p></pre><pre>Regards,<o:p></o:p></pre><pre><o:p>&nbs=
p;</o:p></pre><pre>Dave<o:p></o:p></pre>

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

</div>

</body>

</html>

--_000_701A6382E4B1B0458FC27DE8F6A477081E80B715D9AAEXMSGC424so_--

Delivery-date: Mon, 16 Mar 2009 23:41:24 +0000
Date: Mon, 16 Mar 2009 16:40:38 -0700 (PDT)
Subject: comments on draft-zorn-radius-encattr-15
From: "Dan Harkins" <[email-masked]>
To: [email-masked]

  Hi,

  I just read draft-zorn-radius-encattr-15 and have a few comments.

  - an appendix showing at least two examples (with nice
    ASCII art figures too!) would be most helpful.

  - apparently there is a requirement (unstated) to support
    encryption of random data as well as key wrapping, and to
    be able to authenticate encrypted data. To do this the
    draft mandates AES-CBC-128 (for encryption of arbitrary
    data), AES Key Wrap (for key wrapping), and HMAC-SHA1 to
    integrity check the encrypted data and the rest of the
    message.

    These three tasks could be accomplished by one single
    cipher mode: SIV. SIV can do authentication encryption
    with associated data of arbitrary-sized plaintext when a
    nonce is included in its input, or do deterministic key
    wrapping when a component of the plaintext contains a
    random key.

    Furthermore, there seems to be a desire to integrity check
    a message that does not have any encrypted components. To
    satifsy this requirement (also unstated) the draft mandates
    HMAC-SHA1 instead of AES-CMAC.

    If the draft mandated support for AES-SIV-CMAC to do
    authenticated encryption (with associated data!) and
    AES-CMAC for encryption-less integrity protection then
    it can be implemented with a single primitive. Since
    AES-SIV-CMAC itself uses AES-CMAC you get it for free.
    Then the draft could build upon a single foundation and
    its security would be based on the assumption that AES
    is a secure pseudo-random permutation (which I believe
    is the basis for the proof of both AES-CMAC and AES-SIV).

    I recommend the mandatory-to-implement encryption algorithm
    be AES-SIV-CMAC and the mandatory to implement integrity
    check (when encryption is not used) be AES-CMAC.

  - 3.5 says that "Applications using [Key-Liftime] SHOULD
    consider the beginning of the lifetime to be the point
    in time when the key is first used." Why not when it was
    first exponsed (albeit encrypted)? If there is going to
    be a recommendation I think it would help if there's some
    reasoning to go along with it, otherwise just get rid of
    the recommendation.

  - 3.6 says, "If the data encapsulated in the Encrypted-Data
    TLV represents a cryptographic key and the algorithm
    specified by the Encryption-Type TLV requires the use of
    an initialization vector (IV), this TLV may be used to
    communicate the IV from the RADIUS server to its client."

    Actually, if the encryption algorithm is AES-CBC then this
    TLV is needed whether the data being encrypted is a key or
    not. I think it would be better to say, "If the encryption
    algorithm specified by the Encryption-Type TLV requires an
    IV or the data being protected is not a key then this TLV
    may be used to communicate the IV from the RADIUS server
    to its client."

    Also it MAY be appropriate to use "MAY" instead of "may".

  - 3.7, the "algorithms" in this section might be a nice place
    to mention that AES Key Wrap operates on blocks of 64-bits
    even though the block cipher on which it is based operates
    on 128-bit blocks.

    The input of AES-SIV-CMAC includes associated data so the
    two "algorithms", send and receive, should include mention
    of this fact right after they mention an IV.

  - 3.8, the description should mandate this TLV is also required
    for encryption algorithms that do not produce authenticated
    ciphertext, like AES-CBC.

  - 3.8.1.1 "...the value of the MAC field is a hash..." What
    about when using AES-CMAC? Does that produce a hash too?
    Perhaps "output from a pseudo-random function" would be better.

  - in 3.8.1.1 MAC=MAC-ALG(x,y) while in 3.8.1.2 MAC=HASH-ALG(x,y).
    How about calling making it more generic: MAC=PRF(x,y)?

  - 3.8.2, what about when using AES-SIV? The RFC 5116 interface
    is mentioned in 3.1 and that produces an authenticating tag
    concatenated with encrypted plaintext as a single "ciphertext"
    output. So when AES-SIV is used should the Message-Authentication-
    Code attributes signify individual components of AAD (since
    SIV can take a vector of inputs and not just a single concatenated
    input)? I think using an Encryption-Type TLV with NULL encryption
    to accomodate traditional RADIUS attributes is wrong, it will also
    screw up AES-SIV since AES-SIV will expect an Encryption-Type TLV
    somewhere that says AES-SIV as the type. It would be better to
    define an Envelope TLV to contain traditional RADIUS attributes.

  - 3.8.2: doesn't CMAC-AES return 16 bytes?

  - 3.9, what's the point of the MAC-Randomizer? In the case of key
    wrapping semantic security is achieved because a component of
    the plaintext is a key. In the case of non-key wrapping encryption
    semantic security is achieved by the IV. In the case of an
    unencrypted message I don't see the need for a MAC-Randomizer.
    If I'm missing something then I'd wager some other people are too
    and a justification is in order.

  - 6, what's "the strength of the algorithm used" if that algorithm
    is HMAC-SHA1?

  regards,

  Dan.

Delivery-date: Sun, 15 Mar 2009 19:13:15 +0000
From: "Glen Zorn" <[email-masked]>
To: "'Bernard Aboba'" <[email-masked]>, "'David B. Nelson'" <[email-masked]>
Cc: <[email-masked]>
Subject: RE: IETF 74 Agenda - Take Five
Date: Sun, 15 Mar 2009 12:11:49 -0700

This is a multipart message in MIME format.

------=_NextPart_000_00F3_01C9A567.39BF1B50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

It appears that the "new Tunnel Type Values" draft appears twice on the
agenda, under both "Documents that have completed RADEXT WG Last Call" and
"Working Group Work Items".

From: [email-masked] [mailto:[email-masked]] On
Behalf Of Bernard Aboba
Sent: Wednesday, March 11, 2009 11:22 AM
To: David B. Nelson
Cc: [email-masked]
Subject: IETF 74 Agenda - Take Five

At IETF 74, the RADEXT WG is currently scheduled to meet on Friday, March
27,2009  from 9 AM - 11:30 AM.  Currently the Agenda is as follows:
 
9 AM - 9:10 Preliminaries (10 minutes)
   Blue Sheets
   Note Takers
   Jabber Scribe
   Agenda bashing
   Document Status
 
Documents completing IETF Last Call (15 minutes)
 
9:10 - 9:15 AM  RADIUS Authorization for NAS Management, David Nelson (10
minutes)
http://tools.ietf.org/html/draft-ietf-radext-management-authorization
 
9:15 - 9:25 AM RADIUS Design Guidelines, Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design
 
Documents that have completed RADEXT WG Last Call (35 minutes)
 
9:25 - 9:30 AM New Tunnel Type Values, Abhishek Tiwari (5 minutes)
http://tools.ietf.org/html/draft-tiwari-radext-tunnel-type
 
9:30 AM - 9:40 AM Status-Server, Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server
 
9:40 AM - 9:50 AM Extended RADIUS Attributes, Glen Zorn (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-extended-attributes
 
9:50 AM - 10:00 AM RADIUS Crypto-agility Requirements, David Nelson (20
minutes)
http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements
 
Documents in RADEXT WG last call (10 minutes)
 
10:00 AM - 10:10 AM RADSEC, Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec
 
Working Group Work Items (20 minutes)
 
10:10 AM - 10:20 AM TCP Transport, Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport
 
10:20 AM - 10:30 AM New Tunnel-Type Values, Abhishek Tiwari (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tunnel-type
 
Individual Submissions (50 minutes)
 
10:30 AM - 10:40 AM  NAI-based Dynamic Peer Discovery, Stefan Winter (10
minutes)
http://tools.ietf.org/html/draft-winter-dynamic-discovery
 
10:40 AM - 10:50 AM RADIUS attributes for IPv6 Access Networks, Benoit
Lourdelet (10 minutes)
http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access
 
10:50 AM - 11:00 AM RADIUS Attributes for IEEE 802.16 PKMv1, Glen Zorn (10
minutes)
http://tools.ietf.org/html/draft-zorn-radius-pkmv1
 
11:00 AM - 11:10 AM RADIUS Confidentiality, Glen Zorn (10 minutes)
http://tools.ietf.org/html/draft-zorn-radius-encattr
 
Summary & Wrap-up

------=_NextPart_000_00F3_01C9A567.39BF1B50
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Arial =
Black","sans-serif";
color:#7030A0'>It appears that the &quot;new Tunnel Type Values&quot; =
draft
appears twice on the agenda, under both &quot;</span><span =
style=3D'font-size:
10.0pt;font-family:"Arial Black","sans-serif";color:#7030A0'>Documents =
that
have completed RADEXT WG Last Call&quot; and &quot;Working Group Work =
Items&quot;.</span><span
style=3D'font-size:11.0pt;font-family:"Arial =
Black","sans-serif";color:#7030A0'><o:p></o:p></span></p>

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

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

<div>

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

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
[email-masked] [mailto:[email-masked]] <b>On =
Behalf
Of </b>Bernard Aboba<br>
<b>Sent:</b> Wednesday, March 11, 2009 11:22 AM<br>
<b>To:</b> David B. Nelson<br>
<b>Cc:</b> [email-masked]<br>
<b>Subject:</b> IETF 74 Agenda - Take Five<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'>At
IETF 74, the RADEXT WG is currently scheduled to meet on Friday, March
27,2009&nbsp; from 9 AM - 11:30 AM.&nbsp; Currently the Agenda is as =
follows:<br>
&nbsp;<br>
9 AM - 9:10 Preliminaries (10 minutes)<br>
&nbsp;&nbsp; Blue Sheets<br>
&nbsp;&nbsp; Note Takers<br>
&nbsp;&nbsp; Jabber Scribe<br>
&nbsp;&nbsp; Agenda bashing<br>
&nbsp;&nbsp; Document Status<br>
&nbsp;<br>
Documents completing IETF Last Call (15 minutes)<br>
&nbsp;<br>
9:10 - 9:15 AM&nbsp; RADIUS Authorization for NAS Management, David =
Nelson (10
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-management-authoriza=
tion">http://tools.ietf.org/html/draft-ietf-radext-management-authorizati=
on</a><br>
&nbsp;<br>
9:15 - 9:25 AM RADIUS Design Guidelines, Alan DeKok (10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design">http://tools=
.ietf.org/html/draft-ietf-radext-design</a><br>
&nbsp;<br>
Documents that have completed RADEXT WG Last Call (35 minutes)<br>
&nbsp;<br>
9:25 - 9:30 AM New Tunnel Type Values, Abhishek Tiwari (5 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-tiwari-radext-tunnel-type">http:=
//tools.ietf.org/html/draft-tiwari-radext-tunnel-type</a><br>
&nbsp;<br>
9:30 AM &#8211; 9:40 AM Status-Server, Alan DeKok (10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</a><br>
&nbsp;<br>
9:40 AM &#8211; 9:50 AM Extended RADIUS Attributes, Glen Zorn (10 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-extended-attributes"=
>http://tools.ietf.org/html/draft-ietf-radext-extended-attributes</a><br>=

&nbsp;<br>
9:50 AM - 10:00 AM RADIUS Crypto-agility Requirements, David Nelson (20
minutes)<br>
<a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requi=
rements">http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requ=
irements</a><br>
&nbsp;<br>
Documents in RADEXT WG last call (10 minutes)<br>
&nbsp;<br>
10:00 AM - 10:10 AM RADSEC, Stefan Winter (10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</a><br>
&nbsp;<br>
Working Group Work Items (20 minutes)<br>
&nbsp;<br>
10:10 AM - 10:20 AM TCP Transport, Alan DeKok (10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport">http:=
//tools.ietf.org/html/draft-ietf-radext-tcp-transport</a><br>
&nbsp;<br>
10:20 AM - 10:30 AM New Tunnel-Type Values, Abhishek Tiwari (10 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tunnel-type">http://=
tools.ietf.org/html/draft-ietf-radext-tunnel-type</a><br>
&nbsp;<br>
Individual Submissions (50 minutes)<br>
&nbsp;<br>
10:30 AM - 10:40 AM&nbsp; NAI-based Dynamic Peer Discovery, Stefan =
Winter (10
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-winter-dynamic-discovery">http:/=
/tools.ietf.org/html/draft-winter-dynamic-discovery</a><br>
&nbsp;<br>
10:40 AM - 10:50 AM RADIUS attributes for IPv6 Access Networks, Benoit
Lourdelet (10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access">ht=
tp://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access</a><br>
&nbsp;<br>
10:50 AM - 11:00 AM RADIUS Attributes for IEEE 802.16 PKMv1, Glen Zorn =
(10
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-zorn-radius-pkmv1">http://tools.=
ietf.org/html/draft-zorn-radius-pkmv1</a><br>
&nbsp;<br>
11:00 AM - 11:10 AM RADIUS Confidentiality, Glen Zorn (10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-zorn-radius-encattr">http://tool=
s.ietf.org/html/draft-zorn-radius-encattr</a><br>
&nbsp;<br>
Summary &amp; Wrap-up<o:p></o:p></span></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_00F3_01C9A567.39BF1B50--

Envelope-to: [email-masked]
Delivery-date: Wed, 11 Mar 2009 23:15:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1236813292; bh=bDEl0ElMx6IjN83ul/HOlOGYEJY4og7NjfMgp3WFmuA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=xtbXT2cywxn85ZnqfO5mgTJ/WzmWXijrjAMnT+al/xoSk3mQTB9lJbC7Nh77HZHfTQdsLF9PMmwhEjqb66h+ZyHA45nRgHtGuYyi72biUtuuxHTM9wuuwFBw0DOKXiDhUpYOoPsh5sSWIwfgbWWHDWQ7RsXMM/XPVjwzK6V1Rh8=
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=nYfoMT7YEqZwZNPPsC7MractsX64CUSi02NK0yu6I9BQKcGa2R8jcjOI/k3sHIN/FZPEWR5nXLBYFkTTg8S+hEPOvaF25SMuPknZKeFXTARILOI99HvK2j6q2msqCeaVY2V0h4dFoELs7/s57oo/gZTeLYkIsV03aL5bmbp4Nbs=;
Message-ID: <[email-masked]>
Date: Wed, 11 Mar 2009 16:14:52 -0700 (PDT)
From: Behcet Sarikaya <[email-masked]>
Reply-To: Behcet Sarikaya <[email-masked]>
Subject: Re: Call for Adoption of "RADIUS attributes for IPv6 Access Networks" as a RADEXT WG work item
To: Bernard Aboba <[email-masked]>, "[email-masked]" <[email-masked]>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-642517672-1236813292=:86021"

--0-642517672-1236813292=:86021
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,=0A=A0 I read this draft and have some concerns.=0AThe draft defines=
 3 new attributes. One of them IPv6-Prefix-Information is superfluous in it=
s present form which makes 33%.=0A=A0 I communicated offline with the autho=
rs and I thought they had agreed to change it with another attribute that c=
ontained lifetime field. However I could not see any revised version yet.=
=0A=A0 In its current form the draft is not ready IMHO to become a WG work =
item yet.=0A=0ARegards,=0A=0ABehcet=0A=0A=0A=0A=0A_________________________=
_______=0AFrom: Bernard Aboba <[email-masked]>=0ATo: "radiusext@=
ops.ietf.org" <[email-masked]>=0ASent: Wednesday, March 11, 2009 1:=
10:43 PM=0ASubject: Call for Adoption of "RADIUS attributes for IPv6 Access=
 Networks" as a RADEXT WG work item=0A=0AThis is a call for review of the d=
ocument "RADIUS attributes for IPv6 Access Networks" for adoption as a RADE=
XT WG work item.=A0 This document was=A0discussed at IETF 73, and is being =
targeted at Proposed Standard status. =0A=A0=0AThe document is available fo=
r review here:=0Ahttp://tools.ietf.org/html/draft-lourdelet-radext-ipv6-acc=
ess=0A=0AThis call for review will last until March 30, 2009.=A0 Please sen=
d email to the RADEXT WG mailing list indicating whether you support adopti=
on of this document as a RADEXT WG work item.=A0 If you have comments on th=
e document, please also send these to the list in the format described on t=
he RADEXT WG Issues list:=0Ahttp://www.drizzle.com/~aboba/RADEXT/=0A=0A=0A=
=0A EMAILING FOR SOMETHING OR OTHER=0AJoin me =0A=0A=0A      
--0-642517672-1236813292=:86021
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman, new york, times, serif;=
font-size:14pt"><DIV>Hi all,</DIV>=0A<DIV>&nbsp; I read this draft and have=
 some concerns.</DIV>=0A<DIV>The draft defines 3 new attributes. One of the=
m IPv6-Prefix-Information is superfluous in its present form which makes 33=
%.</DIV>=0A<DIV>&nbsp; I communicated offline with the authors and I though=
t they had agreed to change it with another attribute that contained lifeti=
me field. However I could not see any revised version yet.</DIV>=0A<DIV>&nb=
sp; In its current form the draft is not ready IMHO to become a WG work ite=
m yet.</DIV>=0A<DIV>&nbsp;</DIV>=0A<DIV>Regards,</DIV>=0A<DIV>&nbsp;</DIV>=
=0A<DIV>Behcet<BR></DIV>=0A<DIV style=3D"FONT-SIZE: 14pt; FONT-FAMILY: time=
s new roman, new york, times, serif"><BR>=0A<DIV style=3D"FONT-SIZE: 12pt; =
FONT-FAMILY: times new roman, new york, times, serif"><FONT face=3DTahoma s=
ize=3D2>=0A<HR SIZE=3D1>=0A<B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN=
></B> Bernard Aboba &lt;[email-masked]&gt;<BR><B><SPAN style=3D"=
FONT-WEIGHT: bold">To:</SPAN></B> "[email-masked]" &lt;radiusext@op=
s.ietf.org&gt;<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wed=
nesday, March 11, 2009 1:10:43 PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">S=
ubject:</SPAN></B> Call for Adoption of "RADIUS attributes for IPv6 Access =
Networks" as a RADEXT WG work item<BR></FONT><BR>=0A<STYLE>=0A.hmmessage P=
=0A{=0Amargin:0px;padding:0px;}=0Abody.hmmessage=0A{=0Afont-size:10pt;font-=
family:Verdana;}=0A</STYLE>=0AThis is a call for review of the document "RA=
DIUS attributes for IPv6 Access Networks" for adoption as a RADEXT WG work =
item.&nbsp; This document was&nbsp;discussed at IETF 73, and is being targe=
ted at Proposed Standard status. <BR>&nbsp;<BR>The document is available fo=
r review here:<BR><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #0068cf; FONT-FAMI=
LY: 'Verdana', 'sans-serif'"><A href=3D"http://tools.ietf.org/html/draft-lo=
urdelet-radext-ipv6-access" target=3D_blank rel=3Dnofollow><FONT color=3D#0=
066cc>http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access</FONT><=
/A></SPAN><BR><BR>This call for review will last until March 30, 2009.&nbsp=
; Please send email to the RADEXT WG mailing list indicating whether you su=
pport adoption of this document as a RADEXT WG work item.&nbsp; If you have=
 comments on the document, please also send these to the list in the format=
 described on the RADEXT WG Issues list:<BR><A href=3D"http://www.drizzle.c=
om/~aboba/RADEXT/" target=3D_blank
 rel=3Dnofollow><FONT color=3D#0068cf>http://www.drizzle.com/~aboba/RADEXT/=
</FONT></A><BR><BR><BR>=0A<TABLE style=3D"BORDER-TOP: black 1px solid; FONT=
-WEIGHT: bold; FONT-FAMILY: 'Segoe UI', Tahoma,">=0A<TBODY>=0A<TR>=0A<TD><A=
 style=3D"FONT-SIZE: 9pt; COLOR: #0184cb; TEXT-DECORATION: none" href=3D"ht=
tp://im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_GreaterGood" target=
=3D_blank rel=3Dnofollow><IMG style=3D"BORDER-TOP-STYLE: none; BORDER-RIGHT=
-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none" alt=3D"i'=
m" src=3D"http://gfx1.hotmail.com/mail/w3/ltr/i_charity.gif"> EMAILING FOR =
SOMETHING OR OTHER<BR><SPAN style=3D"PADDING-RIGHT: 24px; PADDING-LEFT: 24p=
x; FONT-SIZE: 8pt; PADDING-BOTTOM: 0px; COLOR: #3fb555; PADDING-TOP: 0px; T=
EXT-DECORATION: underline">Join me</SPAN></A></TD></TR></TBODY></TABLE></DI=
V></DIV></div><br>=0A=0A      </body></html>
--0-642517672-1236813292=:86021--

Delivery-date: Wed, 11 Mar 2009 18:33:01 +0000
Date: Wed, 11 Mar 2009 14:32:29 -0400
Subject: Re: [Issue 287] Re: Cmts on ExtAttrs-05
From: Greg Weber <[email-masked]>
To: Glen Zorn <[email-masked]>
Cc: [email-masked]

I see the issue mentioned below has been fixed in -07, so I think
Issue 287 may be closed.

G

>>> Figure 3: the second Ext-Type's value:
>>> =A0 "(0x00" -> "(0x01)"
>>
>> Fixed.
>
> I don't think this got fixed correctly in -06. =A0Now the first byte of
> Ext-Type is 0x00, and it should be 0x01.
>
> G

Delivery-date: Wed, 11 Mar 2009 18:24:30 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: Request for Slides
Date: Wed, 11 Mar 2009 11:24:10 -0700

--_bb5f71bb-5fa0-46ab-8604-39a987bc3f91_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The RADEXT WG is scheduled to meet on Friday=2C March 27=2C 2009 from 9:00 =
- 11:30 AM.=20

=20

So that we can post the slides well in advance=2C please email these to mys=
elf and/or David by Sunday=2C March 22=2C 2009.=20

 EMAILING FOR THE GREATER GOOD
Join me=

--_bb5f71bb-5fa0-46ab-8604-39a987bc3f91_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
The RADEXT WG is scheduled to meet on Friday=2C March 27=2C 2009&nbsp=3Bfro=
m 9:00 - 11:30 AM. <BR>
&nbsp=3B<BR>
So that we can post the slides well in advance=2C please email these to mys=
elf and/or David by Sunday=2C March 22=2C 2009. <BR><BR><BR>
<TABLE style=3D"BORDER-TOP: black 1px solid=3B FONT-WEIGHT: bold=3B FONT-FA=
MILY: 'Segoe UI'=2CTahoma=2Csan-serif">
<TBODY>
<TR>
<TD><A style=3D"FONT-SIZE: 9pt=3B COLOR: #0184cb=3B TEXT-DECORATION: none" =
href=3D"http://im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_GreaterGood=
"><IMG style=3D"BORDER-TOP-STYLE: none=3B BORDER-RIGHT-STYLE: none=3B BORDE=
R-LEFT-STYLE: none=3B BORDER-BOTTOM-STYLE: none" alt=3D"i'm" src=3D"http://=
gfx1.hotmail.com/mail/w3/ltr/i_charity.gif"> EMAILING FOR THE GREATER GOOD<=
BR><SPAN style=3D"PADDING-RIGHT: 24px=3B PADDING-LEFT: 24px=3B FONT-SIZE: 8=
pt=3B PADDING-BOTTOM: 0px=3B COLOR: #3fb555=3B PADDING-TOP: 0px=3B TEXT-DEC=
ORATION: underline">Join me</SPAN></A></TD></TR></TBODY></TABLE></body>
</html>=

--_bb5f71bb-5fa0-46ab-8604-39a987bc3f91_--

Delivery-date: Wed, 11 Mar 2009 18:22:55 +0000
From: Bernard Aboba <[email-masked]>
To: "David B. Nelson" <[email-masked]>
CC: "[email-masked]" <[email-masked]>
Subject: IETF 74 Agenda - Take Five
Date: Wed, 11 Mar 2009 11:22:26 -0700

--_6cc35ee2-0e50-47fe-b9bc-2db0801de01a_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

At IETF 74=2C the RADEXT WG is currently scheduled to meet on Friday=2C Mar=
ch 27=2C2009  from 9 AM - 11:30 AM.  Currently the Agenda is as follows:
=20
9 AM - 9:10 Preliminaries (10 minutes)
   Blue Sheets
   Note Takers
   Jabber Scribe
   Agenda bashing
   Document Status
=20
Documents completing IETF Last Call (15 minutes)
=20
9:10 - 9:15 AM  RADIUS Authorization for NAS Management=2C David Nelson (10=
 minutes)
http://tools.ietf.org/html/draft-ietf-radext-management-authorization
=20
9:15 - 9:25 AM RADIUS Design Guidelines=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design
=20
Documents that have completed RADEXT WG Last Call (35 minutes)

=20

9:25 - 9:30 AM New Tunnel Type Values=2C Abhishek Tiwari (5 minutes)
http://tools.ietf.org/html/draft-tiwari-radext-tunnel-type
=20
9:30 AM =96 9:40 AM Status-Server=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

=20

9:40 AM =96 9:50 AM Extended RADIUS Attributes=2C Glen Zorn (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-extended-attributes
=20
9:50 AM - 10:00 AM RADIUS Crypto-agility Requirements=2C David Nelson (20 m=
inutes)
http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements
=20
Documents in RADEXT WG last call (10 minutes)

=20

10:00 AM - 10:10 AM RADSEC=2C Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec

=20

Working Group Work Items (20 minutes)
=20
10:10 AM - 10:20 AM TCP Transport=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

=20

10:20 AM - 10:30 AM New Tunnel-Type Values=2C Abhishek Tiwari (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tunnel-type

=20

Individual Submissions (50 minutes)

=20

10:30 AM - 10:40 AM  NAI-based Dynamic Peer Discovery=2C Stefan Winter (10 =
minutes)
http://tools.ietf.org/html/draft-winter-dynamic-discovery

=20

10:40 AM - 10:50 AM RADIUS attributes for IPv6 Access Networks=2C Benoit Lo=
urdelet (10 minutes)
http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access

=20

10:50 AM - 11:00 AM RADIUS Attributes for IEEE 802.16 PKMv1=2C Glen Zorn (1=
0 minutes)
http://tools.ietf.org/html/draft-zorn-radius-pkmv1

=20

11:00 AM - 11:10 AM RADIUS Confidentiality=2C Glen Zorn (10 minutes)
http://tools.ietf.org/html/draft-zorn-radius-encattr

=20

Summary & Wrap-up

--_6cc35ee2-0e50-47fe-b9bc-2db0801de01a_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
At IETF 74=2C the RADEXT WG is currently scheduled to meet on Friday=2C Mar=
ch 27=2C2009&nbsp=3B from 9 AM - 11:30 AM.&nbsp=3B Currently the Agenda is =
as follows:<BR>&nbsp=3B<BR>9 AM - 9:10 Preliminaries (10 minutes)<BR>&nbsp=
=3B&nbsp=3B Blue Sheets<BR>&nbsp=3B&nbsp=3B Note Takers<BR>&nbsp=3B&nbsp=3B=
 Jabber Scribe<BR>&nbsp=3B&nbsp=3B Agenda bashing<BR>&nbsp=3B&nbsp=3B Docum=
ent Status<BR>&nbsp=3B<BR>Documents completing IETF Last Call (15 minutes)<=
BR>&nbsp=3B<BR>9:10 - 9:15 AM&nbsp=3B RADIUS Authorization for NAS Manageme=
nt=2C David Nelson (10 minutes)<BR><A href=3D"http://tools.ietf.org/html/dr=
aft-ietf-radext-management-authorization">http://tools.ietf.org/html/draft-=
ietf-radext-management-authorization</A><BR>&nbsp=3B<BR>9:15 - 9:25 AM RADI=
US Design Guidelines=2C Alan DeKok (10 minutes)<BR><A href=3D"http://tools.=
ietf.org/html/draft-ietf-radext-design">http://tools.ietf.org/html/draft-ie=
tf-radext-design</A><BR>&nbsp=3B<BR>Documents that have completed RADEXT WG=
 Last Call (35 minutes)<BR>
&nbsp=3B<BR>
9:25 - 9:30 AM New Tunnel Type Values=2C Abhishek Tiwari (5 minutes)<BR><A =
href=3D"http://tools.ietf.org/html/draft-tiwari-radext-tunnel-type">http://=
tools.ietf.org/html/draft-tiwari-radext-tunnel-type</A><BR>&nbsp=3B<BR>9:30=
 AM =96 9:40 AM Status-Server=2C Alan DeKok (10 minutes)<BR><A href=3D"http=
://tools.ietf.org/html/draft-ietf-radext-status-server">http://tools.ietf.o=
rg/html/draft-ietf-radext-status-server</A><BR>
&nbsp=3B<BR>
9:40 AM =96 9:50 AM Extended RADIUS Attributes=2C Glen Zorn (10 minutes)<BR=
><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-extended-attribute=
s">http://tools.ietf.org/html/draft-ietf-radext-extended-attributes</A><BR>=
&nbsp=3B<BR>9:50 AM - 10:00 AM RADIUS Crypto-agility Requirements=2C David =
Nelson (20 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-crypto-agility-requirements">http://tools.ietf.org/html/draft-ietf-rade=
xt-crypto-agility-requirements</A><BR>&nbsp=3B<BR>Documents in RADEXT WG la=
st call (10 minutes)<BR>
&nbsp=3B<BR>
10:00 AM - 10:10 AM RADSEC=2C Stefan Winter (10 minutes)<BR><A href=3D"http=
://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools.ietf.org/html=
/draft-ietf-radext-radsec</A><BR>
&nbsp=3B<BR>
Working Group Work Items (20 minutes)<BR>&nbsp=3B<BR>10:10 AM - 10:20 AM TC=
P Transport=2C Alan DeKok (10 minutes)<BR><A href=3D"http://tools.ietf.org/=
html/draft-ietf-radext-tcp-transport">http://tools.ietf.org/html/draft-ietf=
-radext-tcp-transport</A><BR>
&nbsp=3B<BR>
10:20 AM - 10:30 AM New Tunnel-Type Values=2C Abhishek Tiwari (10 minutes)<=
BR><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-tunnel-type">htt=
p://tools.ietf.org/html/draft-ietf-radext-tunnel-type</A><BR>
&nbsp=3B<BR>
Individual Submissions (50 minutes)<BR>
&nbsp=3B<BR>
10:30 AM - 10:40 AM&nbsp=3B NAI-based Dynamic Peer Discovery=2C Stefan Wint=
er (10 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-winter-dynam=
ic-discovery">http://tools.ietf.org/html/draft-winter-dynamic-discovery</A>=
<BR>
&nbsp=3B<BR>
10:40 AM - 10:50 AM RADIUS attributes for IPv6 Access Networks=2C Benoit Lo=
urdelet (10 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-lourdel=
et-radext-ipv6-access">http://tools.ietf.org/html/draft-lourdelet-radext-ip=
v6-access</A><BR>
&nbsp=3B<BR>
10:50 AM - 11:00 AM RADIUS Attributes for IEEE 802.16 PKMv1=2C Glen Zorn (1=
0 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-zorn-radius-pkmv1=
">http://tools.ietf.org/html/draft-zorn-radius-pkmv1</A><BR>
&nbsp=3B<BR>
11:00 AM - 11:10 AM RADIUS Confidentiality=2C Glen Zorn (10 minutes)<BR><A =
href=3D"http://tools.ietf.org/html/draft-zorn-radius-encattr">http://tools.=
ietf.org/html/draft-zorn-radius-encattr</A><BR>
&nbsp=3B<BR>
Summary &amp=3B Wrap-up<BR></body>
</html>=

--_6cc35ee2-0e50-47fe-b9bc-2db0801de01a_--

Delivery-date: Wed, 11 Mar 2009 18:11:06 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: Call for Adoption of "RADIUS attributes for IPv6 Access Networks" as a RADEXT WG work item
Date: Wed, 11 Mar 2009 11:10:43 -0700

--_2d355f99-7f01-45da-a2c4-1f195b12ce33_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is a call for review of the document "RADIUS attributes for IPv6 Acces=
s Networks" for adoption as a RADEXT WG work item.  This document was discu=
ssed at IETF 73=2C and is being targeted at Proposed Standard status.=20

=20
The document is available for review here:
http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access

This call for review will last until March 30=2C 2009.  Please send email t=
o the RADEXT WG mailing list indicating whether you support adoption of thi=
s document as a RADEXT WG work item.  If you have comments on the document=
=2C please also send these to the list in the format described on the RADEX=
T WG Issues list:
http://www.drizzle.com/~aboba/RADEXT/

 EMAILING FOR SOMETHING OR OTHER
Join me=

--_2d355f99-7f01-45da-a2c4-1f195b12ce33_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
This is a call for review of the document "RADIUS attributes for IPv6 Acces=
s Networks" for adoption as a RADEXT WG work item.&nbsp=3B This document wa=
s&nbsp=3Bdiscussed at IETF 73=2C and is being targeted at Proposed Standard=
 status. <BR>
&nbsp=3B<BR>The document is available for review here:<BR><SPAN style=3D"FO=
NT-SIZE: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><=
A href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access" re=
l=3Dnofollow><FONT color=3D#0066cc>http://tools.ietf.org/html/draft-lourdel=
et-radext-ipv6-access</FONT></A></SPAN><BR><BR>This call for review will la=
st until March 30=2C 2009.&nbsp=3B Please send email to the RADEXT WG maili=
ng list indicating whether you support adoption of this document as a RADEX=
T WG work item.&nbsp=3B If you have comments on the document=2C please also=
 send these to the list in the format described on the RADEXT WG Issues lis=
t:<BR><A href=3D"http://www.drizzle.com/~aboba/RADEXT/" target=3D_blank><FO=
NT color=3D#0068cf>http://www.drizzle.com/~aboba/RADEXT/</FONT></A><BR><BR>=
<BR>
<TABLE style=3D"BORDER-TOP: black 1px solid=3B FONT-WEIGHT: bold=3B FONT-FA=
MILY: 'Segoe UI'=2CTahoma=2Csan-serif">
<TBODY>
<TR>
<TD><A style=3D"FONT-SIZE: 9pt=3B COLOR: #0184cb=3B TEXT-DECORATION: none" =
href=3D"http://im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_GreaterGood=
"><IMG style=3D"BORDER-TOP-STYLE: none=3B BORDER-RIGHT-STYLE: none=3B BORDE=
R-LEFT-STYLE: none=3B BORDER-BOTTOM-STYLE: none" alt=3D"i'm" src=3D"http://=
gfx1.hotmail.com/mail/w3/ltr/i_charity.gif"> EMAILING FOR SOMETHING OR OTHE=
R<BR><SPAN style=3D"PADDING-RIGHT: 24px=3B PADDING-LEFT: 24px=3B FONT-SIZE:=
 8pt=3B PADDING-BOTTOM: 0px=3B COLOR: #3fb555=3B PADDING-TOP: 0px=3B TEXT-D=
ECORATION: underline">Join me</SPAN></A></TD></TR></TBODY></TABLE></body>
</html>=

--_2d355f99-7f01-45da-a2c4-1f195b12ce33_--

Delivery-date: Wed, 11 Mar 2009 17:59:01 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: Call for Adoption of "NAI-based Peer Discovery" as a RADEXT WG work item
Date: Wed, 11 Mar 2009 10:58:39 -0700

--_15e20a7f-4291-409c-980b-beb2cea57bbf_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is a call for review of the document "NAI-based Peer Discovery" for ad=
option as a RADEXT WG work item.  This document was formerly part of the RA=
DSEC document=2C and is now being split off into its own document=2C which =
(like RADSEC) will be targeted toward Experimental Status.=20

=20

The document is available for review here:
http://www.ietf.org/internet-drafts/draft-winter-dynamic-discovery-00.txt

This call for review will last until March 30=2C 2009.  Please send email t=
o the RADEXT WG mailing list indicating whether you support adoption of thi=
s document as a RADEXT WG work item.  If you have comments on the document=
=2C please also send these to the list in the format described on the RADEX=
T WG Issues list:

http://www.drizzle.com/~aboba/RADEXT/

=20

 EMAILING FOR MODERATE MEDIOCRITY
Join me=

--_15e20a7f-4291-409c-980b-beb2cea57bbf_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
This is a call for review of the document "NAI-based Peer Discovery" for ad=
option as a RADEXT WG work item.&nbsp=3B This document was formerly part of=
 the RADSEC document=2C and is now being split&nbsp=3Boff into its own docu=
ment=2C which (like RADSEC) will be targeted toward Experimental Status. <B=
R>
&nbsp=3B<BR>
The document is available for review here:<BR>http://www.ietf.org/internet-=
drafts/draft-winter-dynamic-discovery-00.txt<BR><BR>This call for review wi=
ll last until March 30=2C 2009.&nbsp=3B Please send email to the RADEXT WG =
mailing list indicating whether you support adoption of this document as a =
RADEXT WG work item.&nbsp=3B If you have comments on the document=2C please=
 also send these to the list in the format described on the RADEXT WG Issue=
s list:<BR>
<A href=3D"http://www.drizzle.com/~aboba/RADEXT/">http://www.drizzle.com/~a=
boba/RADEXT/</A><BR>
<BR><BR>&nbsp=3B<BR>
<TABLE style=3D"BORDER-TOP: black 1px solid=3B FONT-WEIGHT: bold=3B FONT-FA=
MILY: 'Segoe UI'=2CTahoma=2Csan-serif">
<TBODY>
<TR>
<TD><A style=3D"FONT-SIZE: 9pt=3B COLOR: #0184cb=3B TEXT-DECORATION: none" =
href=3D"http://im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_GreaterGood=
"><IMG style=3D"BORDER-TOP-STYLE: none=3B BORDER-RIGHT-STYLE: none=3B BORDE=
R-LEFT-STYLE: none=3B BORDER-BOTTOM-STYLE: none" alt=3D"i'm" src=3D"http://=
gfx1.hotmail.com/mail/w3/ltr/i_charity.gif"> EMAILING FOR MODERATE MEDIOCRI=
TY<BR><SPAN style=3D"PADDING-RIGHT: 24px=3B PADDING-LEFT: 24px=3B FONT-SIZE=
: 8pt=3B PADDING-BOTTOM: 0px=3B COLOR: #3fb555=3B PADDING-TOP: 0px=3B TEXT-=
DECORATION: underline">Join me</SPAN></A></TD></TR></TBODY></TABLE></body>
</html>=

--_15e20a7f-4291-409c-980b-beb2cea57bbf_--

Delivery-date: Wed, 11 Mar 2009 17:55:22 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: REMINDER:  RADEXT WG last call on RADSEC specification
Date: Wed, 11 Mar 2009 10:54:34 -0700

--_de4c4dc5-1dfa-4aab-be7c-0995c3ac093b_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is a reminder of the ongoing RADEXT WG last call on the RADSEC specifi=
cation=2C prior to sending this document on to the IESG for publication as =
an Experimental RFC.  The document is available for inspection here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-04.txt

RADEXT WG last call will last until March 30=2C 2009.  Please send comments=
 to the RADEXT WG mailing list using the format described in the RADEXT Iss=
ues list (http://www.drizzle.com/~aboba/RADEXT/). =20

 EMAILING FOR THE LESSER BAD
Join me=

--_de4c4dc5-1dfa-4aab-be7c-0995c3ac093b_
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'>

<TABLE width=3D"100%">
<TBODY>
<TR>
<TD>
<P>This is a reminder of the ongoing RADEXT WG last call on the RADSEC spec=
ification=2C prior to sending this document on to the IESG for publication =
as an Experimental RFC.&nbsp=3B The document is available for inspection he=
re:<BR><A href=3D"http://www.ietf.org/internet-drafts/draft-ietf-radext-rad=
sec-04.txt">http://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-04=
.txt</A><BR>
<BR>RADEXT WG last call will last until March 30=2C 2009.&nbsp=3B Please se=
nd comments to the RADEXT WG mailing list using the format described in the=
 RADEXT Issues list (http://www.drizzle.com/~aboba/RADEXT/).&nbsp=3B <BR></=
TD></TR></TBODY></TABLE><BR><BR></P>
<TABLE style=3D"BORDER-TOP: black 1px solid=3B FONT-WEIGHT: bold=3B FONT-FA=
MILY: 'Segoe UI'=2CTahoma=2Csan-serif">
<TBODY>
<TR>
<TD><A style=3D"FONT-SIZE: 9pt=3B COLOR: #0184cb=3B TEXT-DECORATION: none" =
href=3D"http://im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_GreaterGood=
"><IMG style=3D"BORDER-TOP-STYLE: none=3B BORDER-RIGHT-STYLE: none=3B BORDE=
R-LEFT-STYLE: none=3B BORDER-BOTTOM-STYLE: none" alt=3D"i'm" src=3D"http://=
gfx1.hotmail.com/mail/w3/ltr/i_charity.gif"> EMAILING FOR THE LESSER BAD<BR=
><SPAN style=3D"PADDING-RIGHT: 24px=3B PADDING-LEFT: 24px=3B FONT-SIZE: 8pt=
=3B PADDING-BOTTOM: 0px=3B COLOR: #3fb555=3B PADDING-TOP: 0px=3B TEXT-DECOR=
ATION: underline">Join me</SPAN></A></TD></TR></TBODY></TABLE></body>
</html>=

--_de4c4dc5-1dfa-4aab-be7c-0995c3ac093b_--

Delivery-date: Tue, 10 Mar 2009 03:35:32 +0000
From: "Dave Nelson" <[email-masked]>
To: <[email-masked]>
Cc: <[email-masked]>
Subject: RE: FW: [Isms] radius usage last call followup
Date: Mon, 9 Mar 2009 23:35:09 -0400

Alan DeKok writes...

> > Please check the changes until March 23rd.
> >   Security Section:
> 
>    There are good reasons to provision USM access so supplement with
>    AAA-based access, however.
> 
> 
>  NIT: This doesn't appear to be a sentence.

Yeah.  Let's see what that was supposed to say...  I think it's:

    There are good reasons to provision USM access to supplement
    AAA-based access, however.

Delivery-date: Tue, 10 Mar 2009 03:12:43 +0000
Date: Tue, 10 Mar 2009 04:11:36 +0100
From: Alan DeKok <[email-masked]>
To: [email-masked]
Subject: Re: FW: [Isms] radius usage last call followup

Romascanu, Dan (Dan) wrote:
> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]] On Behalf Of
> Juergen Schoenwaelder
...
> our radius usage document has been last called in November and the
> comments lead to several changes. The revised ID is now in place:
> 
>   http://tools.ietf.org/html/draft-ietf-isms-radius-usage-05
> 
> Please check the changes until March 23rd.

  Security Section:

   There are good reasons to provision USM access so supplement with
   AAA-based access, however.

 NIT: This doesn't appear to be a sentence.

  Alan DeKok.

Delivery-date: Mon, 09 Mar 2009 22:09:17 +0000
From: "Glen Zorn" <[email-masked]>
To: "'Bernard Aboba'" <[email-masked]>, "'David B. Nelson'" <[email-masked]>
Cc: <[email-masked]>
Subject: RE: IETF 74 Agenda - Take Four
Date: Mon, 9 Mar 2009 15:07:51 -0700

This is a multipart message in MIME format.

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

Please allocate a slot under "Individual Submissions" for
http://www.ietf.org/internet-drafts/draft-zorn-radius-pkmv1-03.txt.  Thanks!

From: [email-masked] [mailto:[email-masked]] On
Behalf Of Bernard Aboba
Sent: Wednesday, March 04, 2009 2:11 PM
To: [email-masked]
Subject: IETF 74 Agenda - Take Four

At IETF 74, the RADEXT WG is currently scheduled to meet on Friday, March
27,2009  from 9 AM - 11:30 AM.  Currently the Agenda is as follows:
 
9 AM - 9:10 Preliminaries (10 minutes)
   Blue Sheets
   Note Takers
   Jabber Scribe
   Agenda bashing
   Document Status
 
Documents completing IETF Last Call (20 minutes)
 
9:10 - 9:20 AM  RADIUS Authorization for NAS Management, David Nelson (10
minutes)
http://tools.ietf.org/html/draft-ietf-radext-management-authorization
 
9:20 - 9:30 AM RADIUS Design Guidelines, Alan DeKok (10 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-design>
http://tools.ietf.org/html/draft-ietf-radext-design
 
Documents that have completed RADEXT WG Last Call (50 minutes)
 
9:30 AM - 9:40 AM Status-Server, Alan DeKok (10 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-status-server>
http://tools.ietf.org/html/draft-ietf-radext-status-server

9:40 AM - 9:50 AM RADSEC, Stefan Winter (10 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-radsec>
http://tools.ietf.org/html/draft-ietf-radext-radsec
 
9:50 AM - 10:00 AM Extended RADIUS Attributes, TBD (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-extended-attributes
 
10:00 AM - 10:20 AM RADIUS Crypto-agility Requirements, David Nelson (20
minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements>
http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements

Working Group Work Items (20 minutes)
 
10:20 AM - 10:30 AM TCP Transport, Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:30 AM - 10:40 AM New Tunnel-Type Values, Abhishek Tiwari (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tunnel-type

Individual Submissions (20 minutes)

10:40 AM - 10:50 AM  NAI-based Dynamic Peer Discovery, Stefan Winter (10
minutes)

http://tools.ietf.org/html/draft-winter-dynamic-discovery

10:50 - 11:00 AM RADIUS attributes for IPv6 Access Networks, Benoit
Lourdelet (10 minutes)

http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access

Summary & Wrap-up

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

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Arial =
Black","sans-serif";
color:#7030A0'>Please allocate a slot under &quot;Individual =
Submissions&quot;
for <a =
href=3D"http://www.ietf.org/internet-drafts/draft-zorn-radius-pkmv1-03.tx=
t">http://www.ietf.org/internet-drafts/draft-zorn-radius-pkmv1-03.txt</a>=
.&nbsp;
Thanks!<o:p></o:p></span></p>

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

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

<div>

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

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
[email-masked] [mailto:[email-masked]] <b>On =
Behalf
Of </b>Bernard Aboba<br>
<b>Sent:</b> Wednesday, March 04, 2009 2:11 PM<br>
<b>To:</b> [email-masked]<br>
<b>Subject:</b> IETF 74 Agenda - Take Four<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#444444'>At IETF 74, the RADEXT WG is currently scheduled to meet =
on
Friday, March 27,2009&nbsp; from 9 AM - 11:30 AM.&nbsp; Currently the =
Agenda is
as follows:<br>
&nbsp;<br>
9 AM - 9:10 Preliminaries (10 minutes)<br>
&nbsp;&nbsp; Blue Sheets<br>
&nbsp;&nbsp; Note Takers<br>
&nbsp;&nbsp; Jabber Scribe<br>
&nbsp;&nbsp; Agenda bashing<br>
&nbsp;&nbsp; Document Status<br>
&nbsp;<br>
Documents completing IETF&nbsp;Last Call&nbsp;(20 minutes)<br>
&nbsp;<br>
9:10 - 9:20 AM&nbsp; RADIUS Authorization for NAS Management, David =
Nelson (10
minutes)<br>
</span><u><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#0066CC'><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-management-authoriza=
tion">http://tools.ietf.org/html/draft-ietf-radext-management-authorizati=
on</a></span></u><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#44444=
4'><br>
&nbsp;<br>
9:20 - 9:30 AM RADIUS Design Guidelines, Alan DeKok (10 minutes)<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-radext-design"><span
style=3D'color:#0066CC'>http://tools.ietf.org/html/draft-ietf-radext-desi=
gn</span></a><br>
&nbsp;<br>
Documents that have completed RADEXT WG Last Call (50 =
minutes)</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
&nbsp;<br>
<span style=3D'color:#444444'>9:30 AM &#8211; 9:40 AM Status-Server, =
Alan DeKok
(10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server"><span=

style=3D'color:purple'>http://tools.ietf.org/html/draft-ietf-radext-statu=
s-server</span></a><br>
<br>
9:40 AM - 9:50 AM RADSEC, Stefan Winter (10 minutes)<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec"><span
style=3D'color:#0066CC'>http://tools.ietf.org/html/draft-ietf-radext-rads=
ec</span></a><br>
&nbsp;<br>
9:50 AM &#8211;&nbsp;10:00 AM Extended RADIUS Attributes, TBD (10 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-extended-attributes"=
>http://tools.ietf.org/html/draft-ietf-radext-extended-attributes</a><br>=

&nbsp;<br>
10:00 AM - 10:20 AM RADIUS Crypto-agility Requirements, David Nelson (20
minutes)<br>
<a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requi=
rements"><span
style=3D'color:#0066CC'>http://tools.ietf.org/html/draft-ietf-radext-cryp=
to-agility-requirements</span></a></span><o:p></o:p></span></p>

<div>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#444444'>&nbsp;<br>
Working Group Work Items (20 minutes)<br>
&nbsp;<br>
10:20 AM - 10:30 AM TCP Transport, Alan DeKok (10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport">http:=
//tools.ietf.org/html/draft-ietf-radext-tcp-transport</a><br>
<br>
10:30 AM - 10:40 AM New Tunnel-Type Values, Abhishek Tiwari (10 =
minutes)<br>
</span><u><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#0066CC'><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tunnel-type">http://=
tools.ietf.org/html/draft-ietf-radext-tunnel-type</a></span></u><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#44444=
4'><br>
<br>
Individual Submissions (20 minutes)</span><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#444444'>&nbsp;</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#444444'>10:40 AM - 10:50 =
AM&nbsp;
NAI-based Dynamic Peer Discovery, Stefan Winter (10 minutes)</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#0068CF'><a
href=3D"http://tools.ietf.org/html/draft-winter-dynamic-discovery">http:/=
/tools.ietf.org/html/draft-winter-dynamic-discovery</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:50 - 11:00 AM <span
class=3Dh1>RADIUS attributes for IPv6 Access =
Networks</span><strong><span
style=3D'font-family:"Verdana","sans-serif"'>, </span></strong>Benoit =
Lourdelet
(10 minutes)</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#0068CF'><a
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access">ht=
tp://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access</a></span><sp=
an
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#444444'><br>
Summary &amp; Wrap-up</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<table class=3DMsoNormalTable border=3D1 cellpadding=3D0 =
style=3D'border:none;
 border-top:solid black 1.0pt'>
 <tr>
  <td style=3D'border:none;padding:.75pt .75pt .75pt .75pt'></td>
 </tr>
</table>

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

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_045F_01C9A0C8.D79BB8E0--

Delivery-date: Mon, 09 Mar 2009 21:46:09 +0000
From: [email-masked]
To: [email-masked]
Cc: [email-masked]
Subject: I-D Action:draft-ietf-radext-extended-attributes-07.txt 
Date: Mon,  9 Mar 2009 14:45:01 -0700 (PDT)

--NextPart

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

	Title           : Extended Remote Authentication Dial In User Service (RADIUS) Attributes
	Author(s)       : Y. Li, et al.
	Filename        : draft-ietf-radext-extended-attributes-07.txt
	Pages           : 13
	Date            : 2009-03-09

For the Remote Authentication Dial In User Service (RADIUS) protocol
to continue to support new applications, the RADIUS attribute type
space must be extended beyond the current limit of 255 possible
attribute types while maintaining backwards compatibility with the
existing protocol.  This document defines a mechanism to accomplish
that task, along with standard methods to group together related
attributes and to encode values that don't fit into 253 octets.

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

Content-Type: text/plain
Content-ID:     <[email-masked]>

--NextPart--

Delivery-date: Mon, 09 Mar 2009 19:33:20 +0000
Content-class: urn:content-classes:message
Subject: FW: [Isms] radius usage last call followup
Date: Mon, 9 Mar 2009 20:32:07 +0100
From: "Romascanu, Dan (Dan)" <[email-masked]>
To: <[email-masked]>

=20

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf Of
Juergen Schoenwaelder
Sent: Monday, March 09, 2009 9:31 AM
To: [email-masked]
Subject: [Isms] radius usage last call followup

Hi,

our radius usage document has been last called in November and the
comments lead to several changes. The revised ID is now in place:

  http://tools.ietf.org/html/draft-ietf-isms-radius-usage-05

Please check the changes until March 23rd.

/js

--=20
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
Isms mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/isms

Envelope-to: [email-masked]
Delivery-date: Mon, 09 Mar 2009 13:57:13 +0000
To: IETF-Announce <[email-masked]> 
From: The IESG <[email-masked]>
Subject: Last Call: draft-ietf-radext-design (RADIUS Design Guidelines)  to BCP 
Reply-to: [email-masked]
CC: <[email-masked]>
Message-Id: <[email-masked]>
Date: Mon,  9 Mar 2009 06:55:43 -0700 (PDT)

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

- 'RADIUS Design Guidelines '
   <draft-ietf-radext-design-07.txt> as a BCP

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
[email-masked] mailing lists by 2009-03-23. Exceptionally, 
comments may be sent to [email-masked] 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-design-07.txt

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

The following IPR Declarations may be related to this I-D:

Delivery-date: Mon, 09 Mar 2009 02:09:51 +0000
Date: Sun, 8 Mar 2009 22:08:44 -0400
Subject: [Issue 287] Re: Cmts on ExtAttrs-05
From: Greg Weber <[email-masked]>
To: Glen Zorn <[email-masked]>
Cc: [email-masked]

On Thu, Nov 6, 2008 at 10:09 PM, Glen Zorn <[email-masked]> wrote:
> Greg Weber [mailto:[email-masked]] writes:
>
> ...
>
>> A couple editorial comments on the current (-05) extended attributes
>> draft:
>>
>> Section 5, under More bit description:
>> =A0 =A0"exceeds 246 octets" -> "exceeds 245 octets"
>
> Fixed.
>
>> Section 5, under Ext-Len description:
>> =A0 ">=3D3." -> ">=3D4."
>
> Fixed.
>
>> Figure 3: the second Ext-Type's value:
>> =A0 "(0x00" -> "(0x01)"
>
> Fixed.

I don't think this got fixed correctly in -06.  Now the first byte of
Ext-Type is 0x00, and it should be 0x01.

G

>
>> Figure 4: I think the very last two octet values swapped.
>
> Fixed.
>
>> Figure 4: The third attribute in this figure violates this earlier
>> MUST from section 4:
>
> Yup. =A0Anybody happen to remember whose idea it was to put that restrict=
ion
> in place?
>
>> =A0 "If an Extended Attribute contains more than one TLV then all of the
>> encapsulated
>> =A0 TLVs MUST fit completely within the Extended Attribute."
>> =A0 Not sure if this is a problem with the text or the example -or maybe
>> just wording.
>
>

Delivery-date: Sat, 07 Mar 2009 23:31:39 +0000
From: [email-masked]
To: [email-masked]
Cc: [email-masked]
Subject: I-D Action:draft-ietf-radext-extended-attributes-06.txt 
Date: Sat,  7 Mar 2009 15:30:01 -0800 (PST)

--NextPart

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

	Title           : Extended Remote Authentication Dial In User Service (RADIUS) Attributes
	Author(s)       : Y. Li, et al.
	Filename        : draft-ietf-radext-extended-attributes-06.txt
	Pages           : 13
	Date            : 2009-03-07

For the Remote Authentication Dial In User Service (RADIUS) protocol
to continue to support new applications, the RADIUS attribute type
space must be extended beyond the current limit of 255 possible
attribute types while maintaining backwards compatibility with the
existing protocol.  This document defines a mechanism to accomplish
that task, along with standard methods to group together related
attributes and to encode values that don't fit into 253 octets.

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

Content-Type: text/plain
Content-ID:     <[email-masked]>

--NextPart--

Delivery-date: Fri, 06 Mar 2009 18:59:00 +0000
From: "Glen Zorn" <[email-masked]>
To: "'Bernard Aboba'" <[email-masked]>
Cc: <[email-masked]>
Subject: RE: IETF 74 Agenda - Take Four
Date: Fri, 6 Mar 2009 10:57:39 -0800

This is a multipart message in MIME format.

------=_NextPart_000_0075_01C99E4A.5E7EDA30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I notice that the Encrypted Attributes draft
(http://www.ietf.org/internet-drafts/draft-zorn-radius-encattr-15.txt) is
not on the agenda; may we have a slot, please?  BTW, I'll talk about the
Extended Attributes draft.

From: [email-masked] [mailto:[email-masked]] On
Behalf Of Bernard Aboba
Sent: Wednesday, March 04, 2009 2:11 PM
To: [email-masked]
Subject: IETF 74 Agenda - Take Four

At IETF 74, the RADEXT WG is currently scheduled to meet on Friday, March
27,2009  from 9 AM - 11:30 AM.  Currently the Agenda is as follows:
 
9 AM - 9:10 Preliminaries (10 minutes)
   Blue Sheets
   Note Takers
   Jabber Scribe
   Agenda bashing
   Document Status
 
Documents completing IETF Last Call (20 minutes)
 
9:10 - 9:20 AM  RADIUS Authorization for NAS Management, David Nelson (10
minutes)
http://tools.ietf.org/html/draft-ietf-radext-management-authorization
 
9:20 - 9:30 AM RADIUS Design Guidelines, Alan DeKok (10 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-design>
http://tools.ietf.org/html/draft-ietf-radext-design
 
Documents that have completed RADEXT WG Last Call (50 minutes)
 
9:30 AM - 9:40 AM Status-Server, Alan DeKok (10 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-status-server>
http://tools.ietf.org/html/draft-ietf-radext-status-server

9:40 AM - 9:50 AM RADSEC, Stefan Winter (10 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-radsec>
http://tools.ietf.org/html/draft-ietf-radext-radsec
 
9:50 AM - 10:00 AM Extended RADIUS Attributes, TBD (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-extended-attributes
 
10:00 AM - 10:20 AM RADIUS Crypto-agility Requirements, David Nelson (20
minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements>
http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements

Working Group Work Items (20 minutes)
 
10:20 AM - 10:30 AM TCP Transport, Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:30 AM - 10:40 AM New Tunnel-Type Values, Abhishek Tiwari (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tunnel-type

Individual Submissions (20 minutes)

10:40 AM - 10:50 AM  NAI-based Dynamic Peer Discovery, Stefan Winter (10
minutes)

http://tools.ietf.org/html/draft-winter-dynamic-discovery

10:50 - 11:00 AM RADIUS attributes for IPv6 Access Networks, Benoit
Lourdelet (10 minutes)

http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access

Summary & Wrap-up

------=_NextPart_000_0075_01C99E4A.5E7EDA30
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Arial =
Black","sans-serif";
color:#7030A0'>I notice that the Encrypted Attributes draft (<a
href=3D"http://www.ietf.org/internet-drafts/draft-zorn-radius-encattr-15.=
txt">http://www.ietf.org/internet-drafts/draft-zorn-radius-encattr-15.txt=
</a>)
is not on the agenda; may we have a slot, please?&nbsp; BTW, I'll talk =
about
the Extended Attributes draft&#8230;<o:p></o:p></span></p>

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

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

<div>

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

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
[email-masked]
[mailto:[email-masked]] <b>On Behalf Of </b>Bernard =
Aboba<br>
<b>Sent:</b> Wednesday, March 04, 2009 2:11 PM<br>
<b>To:</b> [email-masked]<br>
<b>Subject:</b> IETF 74 Agenda - Take Four<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#444444'>At IETF 74, the RADEXT WG is currently scheduled to meet =
on
Friday, March 27,2009&nbsp; from 9 AM - 11:30 AM.&nbsp; Currently the =
Agenda is
as follows:<br>
&nbsp;<br>
9 AM - 9:10 Preliminaries (10 minutes)<br>
&nbsp;&nbsp; Blue Sheets<br>
&nbsp;&nbsp; Note Takers<br>
&nbsp;&nbsp; Jabber Scribe<br>
&nbsp;&nbsp; Agenda bashing<br>
&nbsp;&nbsp; Document Status<br>
&nbsp;<br>
Documents completing IETF&nbsp;Last Call&nbsp;(20 minutes)<br>
&nbsp;<br>
9:10 - 9:20 AM&nbsp; RADIUS Authorization for NAS Management, David =
Nelson (10
minutes)<br>
</span><u><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#0066CC'><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-management-authoriza=
tion">http://tools.ietf.org/html/draft-ietf-radext-management-authorizati=
on</a></span></u><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#44444=
4'><br>
&nbsp;<br>
9:20 - 9:30 AM RADIUS Design Guidelines, Alan DeKok (10 minutes)<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-radext-design"><span
style=3D'color:#0066CC'>http://tools.ietf.org/html/draft-ietf-radext-desi=
gn</span></a><br>
&nbsp;<br>
Documents that have completed RADEXT WG Last Call (50 =
minutes)</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
&nbsp;<br>
<span style=3D'color:#444444'>9:30 AM &#8211; 9:40 AM Status-Server, =
Alan DeKok
(10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server"><span=

style=3D'color:purple'>http://tools.ietf.org/html/draft-ietf-radext-statu=
s-server</span></a><br>
<br>
9:40 AM - 9:50 AM RADSEC, Stefan Winter (10 minutes)<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec"><span
style=3D'color:#0066CC'>http://tools.ietf.org/html/draft-ietf-radext-rads=
ec</span></a><br>
&nbsp;<br>
9:50 AM &#8211;&nbsp;10:00 AM Extended RADIUS Attributes, TBD (10 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-extended-attributes"=
>http://tools.ietf.org/html/draft-ietf-radext-extended-attributes</a><br>=

&nbsp;<br>
10:00 AM - 10:20 AM RADIUS Crypto-agility Requirements, David Nelson (20
minutes)<br>
<a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requi=
rements"><span
style=3D'color:#0066CC'>http://tools.ietf.org/html/draft-ietf-radext-cryp=
to-agility-requirements</span></a></span><o:p></o:p></span></p>

<div>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#444444'>&nbsp;<br>
Working Group Work Items (20 minutes)<br>
&nbsp;<br>
10:20 AM - 10:30 AM TCP Transport, Alan DeKok (10 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport">http:=
//tools.ietf.org/html/draft-ietf-radext-tcp-transport</a><br>
<br>
10:30 AM - 10:40 AM New Tunnel-Type Values, Abhishek Tiwari (10 =
minutes)<br>
</span><u><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#0066CC'><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tunnel-type">http://=
tools.ietf.org/html/draft-ietf-radext-tunnel-type</a></span></u><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#44444=
4'><br>
<br>
Individual Submissions (20 minutes)</span><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#444444'>&nbsp;</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#444444'>10:40 AM - 10:50 =
AM&nbsp;
NAI-based Dynamic Peer Discovery, Stefan Winter (10 minutes)</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#0068CF'><a
href=3D"http://tools.ietf.org/html/draft-winter-dynamic-discovery">http:/=
/tools.ietf.org/html/draft-winter-dynamic-discovery</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:50 - 11:00 AM <span
class=3Dh1>RADIUS attributes for IPv6 Access =
Networks</span><strong><span
style=3D'font-family:"Verdana","sans-serif"'>, </span></strong>Benoit =
Lourdelet
(10 minutes)</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#0068CF'><a
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access">ht=
tp://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access</a></span><sp=
an
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'background:white'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#444444'><br>
Summary &amp; Wrap-up</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p>=
</span></p>

<table class=3DMsoNormalTable border=3D1 cellpadding=3D0 =
style=3D'border:none;
 border-top:solid black 1.0pt'>
 <tr>
  <td style=3D'border:none;padding:.75pt .75pt .75pt .75pt'></td>
 </tr>
</table>

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

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_0075_01C99E4A.5E7EDA30--

Delivery-date: Fri, 06 Mar 2009 13:00:47 +0000
Date: Fri, 06 Mar 2009 14:00:13 +0100
From: Stefan Winter <[email-masked]>
To: [email-masked]
Subject: Re: I-D Action:draft-ietf-radext-radsec-04.txt

Hello,

> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-04.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>   

This revision includes updated text to Joe's recent comments. It also
features the new trust language (pre5378 is used). I had to restore my
XML source from a fairly recent backup. I don't expect that text was
lost. Just in case: if I promised a text update to someone "in the next
revision", and that text is not here, please yell.

Please use this updated version as basis for your WGLC comments.

Greetings,

Stefan Winter

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

Tel: +352 424409 1
Fax: +352 422473

Delivery-date: Fri, 06 Mar 2009 12:46:31 +0000
From: [email-masked]
To: [email-masked]
Cc: [email-masked]
Subject: I-D Action:draft-ietf-radext-radsec-04.txt 
Date: Fri,  6 Mar 2009 04:45:01 -0800 (PST)

--NextPart

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

	Title           : TLS encryption for RADIUS over TCP (RadSec)
	Author(s)       : S. Winter, et al.
	Filename        : draft-ietf-radext-radsec-04.txt
	Pages           : 16
	Date            : 2009-03-06

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

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

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

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

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

Content-Type: text/plain
Content-ID:     <[email-masked]>

--NextPart--

Delivery-date: Fri, 06 Mar 2009 08:35:13 +0000
Content-class: urn:content-classes:message
Subject: RE: IETF 74 Agenda - Take Four
Date: Fri, 6 Mar 2009 09:34:06 +0100
From: "Benoit Lourdelet (blourdel)" <[email-masked]>
To: <[email-masked]>, "Bernard Aboba" <[email-masked]>, "Behcet Sarikaya" <[email-masked]>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C99E36.559782F2
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

------_=_NextPart_001_01C99E36.559782F2
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

------_=_NextPart_001_01C99E36.559782F2--

Delivery-date: Thu, 05 Mar 2009 23:16:32 +0000
From: [email-masked]
To: [email-masked]
Cc: [email-masked]
Subject: I-D ACTION:draft-ietf-radext-design-07.txt 
Date: Thu,  5 Mar 2009 15:15:01 -0800 (PST)

--NextPart

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

	Title		: RADIUS Design Guidelines
	Author(s)	: G. Weber, A. DeKok
	Filename	: draft-ietf-radext-design-07.txt
	Pages		: 37
	Date		: 2009-3-5
	
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-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-design-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--NextPart--

Envelope-to: [email-masked]
Delivery-date: Thu, 05 Mar 2009 17:21:42 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1236273676; bh=W56w3gMGnF/MM9pC1CuQRFBzPgtiHeCp3UfmG0maDoU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Hk5xgYEQJmvrap8VwYDcuPFrAgkrhmUIUGWEKJCrvtwAMVeRpNIWeVqRq8pqP+iDVhnN9ZXkiGn2a0yC07ZXJQHXooGWdbT4GOlXwYIN1GG2rx32G/5xDKWPG/39jhppmphg7cuHblOO2fZphGV5KfjwbPJke1ptHjyI8XMOzDk=
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=PFjm0Zhi7LxOzij2AszD1o0oR6ZJCiGMhwftIwgD7L/Zr9Ny84LPhEM+EtSMPKDgZ9e5asmsCW9PmGFnehj/1avD6r7P7NTleVXgS4MkwybBb1z2rmM/DomNFt4VF1CDGHTMLEASZ8/iWlzK5qI4aJ9KZsJFzBJFrp0zHUA4Pc8=;
Message-ID: <[email-masked]>
Date: Thu, 5 Mar 2009 09:21:16 -0800 (PST)
From: Behcet Sarikaya <[email-masked]>
Reply-To: Behcet Sarikaya <[email-masked]>
Subject: Re: IETF 74 Agenda - Take Four
To: "Benoit Lourdelet \(blourdel\)" <[email-masked]>
Cc: [email-masked], Bernard Aboba <[email-masked]>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1130777627-1236273676=:19441"

--0-1130777627-1236273676=:19441
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Benoit,=0A=C2=A0 Were you in Minneapolis last November?=0A=0AI think tha=
t draft-lourdelet-radext-rfc3162bis-02 is in line with what was agreed upon=
 and what Bernard had suggested that we do.=0A=0AI think that draft-lourdel=
et-radext-ipv6-access-00 is not.=0A=0AMerci,=0A=0ABehcet=0A=0A=0A=0A=0A____=
____________________________=0AFrom: Benoit Lourdelet (blourdel) <blourdel@=
cisco.com>=0ATo: Behcet Sarikaya <[email-masked]>=0ACc: [email-masked]=
tf.org; Bernard Aboba <[email-masked]>=0ASent: Thursday, March 5=
, 2009 11:03:00 AM=0ASubject: RE: IETF 74 Agenda - Take Four=0A=0A=0AHello,=
=0A=C2=A0=0AFWI : draft-lourdelet-radext-rfc3162bis-02 morphed into draft-l=
ourdelet-radext-ipv6-access-00=0A=C2=A0=0ABenoit =0A=C2=A0=0A=C2=A0=0A=C2=
=A0=0AFrom:[email-masked] [mailto:[email-masked]=
g] On Behalf Of Behcet Sarikaya=0ASent: Thursday, March 05, 2009 5:50 PM=0A=
To: Bernard Aboba; [email-masked]=0ASubject: Re: IETF 74 Agenda - T=
ake Four=0A=C2=A0=0AHi Bernard,=0A=C2=A0 Can you please squeeze a short pre=
sentation for draft-sarikaya-radext-prefix-authorization-02? We are revisin=
g the draft in view of draft-lourdelet-radext-rfc3162bis-02.=0A=C2=A0=0AReg=
ards,=0A=C2=A0=0ABehcet=0A=C2=A0=0A=0A________________________________=0A=
=0AFrom:Bernard Aboba <[email-masked]>=0ATo: "[email-masked]=
..org" <[email-masked]>=0ASent: Wednesday, March 4, 2009 4:11:02 PM=
=0ASubject: IETF 74 Agenda - Take Four=0A=0AAt IETF 74, the RADEXT WG is cu=
rrently scheduled to meet on Friday, March 27,2009=C2=A0 from 9 AM - 11:30 =
AM.=C2=A0 Currently the Agenda is as follows:=0A=C2=A0=0A9 AM - 9:10 Prelim=
inaries (10 minutes)=0A=C2=A0=C2=A0 Blue Sheets=0A=C2=A0=C2=A0 Note Takers=
=0A=C2=A0=C2=A0 Jabber Scribe=0A=C2=A0=C2=A0 Agenda bashing=0A=C2=A0=C2=A0 =
Document Status=0A=C2=A0=0ADocuments completing IETF=C2=A0Last Call=C2=A0(2=
0 minutes)=0A=C2=A0=0A9:10 - 9:20 AM=C2=A0 RADIUS Authorization for NAS Man=
agement, David Nelson (10 minutes)=0Ahttp://tools.ietf.org/html/draft-ietf-=
radext-management-authorization=0A=C2=A0=0A9:20 - 9:30 AM RADIUS Design Gui=
delines, Alan DeKok (10 minutes)=0Ahttp://tools.ietf.org/html/draft-ietf-ra=
dext-design=0A=C2=A0=0ADocuments that have completed RADEXT WG Last Call (5=
0 minutes)=0A=C2=A0=0A9:30 AM =E2=80=93 9:40 AM Status-Server, Alan DeKok (=
10 minutes)=0Ahttp://tools.ietf.org/html/draft-ietf-radext-status-server=0A=
=0A9:40 AM - 9:50 AM RADSEC, Stefan Winter (10 minutes)=0Ahttp://tools.ietf=
..org/html/draft-ietf-radext-radsec=0A=C2=A0=0A9:50 AM =E2=80=93=C2=A010:00 =
AM Extended RADIUS Attributes, TBD (10 minutes)=0Ahttp://tools.ietf.org/htm=
l/draft-ietf-radext-extended-attributes=0A=C2=A0=0A10:00 AM - 10:20 AM RADI=
US Crypto-agility Requirements, David Nelson (20 minutes)=0Ahttp://tools.ie=
tf.org/html/draft-ietf-radext-crypto-agility-requirements=0A=C2=A0=0AWorkin=
g Group Work Items (20 minutes)=0A=C2=A0=0A10:20 AM - 10:30 AM TCP Transpor=
t, Alan DeKok (10 minutes)=0Ahttp://tools.ietf.org/html/draft-ietf-radext-t=
cp-transport=0A=0A10:30 AM - 10:40 AM New Tunnel-Type Values, Abhishek Tiwa=
ri (10 minutes)=0Ahttp://tools.ietf.org/html/draft-ietf-radext-tunnel-type=
=0A=0AIndividual Submissions (20 minutes)=0A=C2=A0=0A10:40 AM - 10:50 AM=C2=
=A0 NAI-based Dynamic Peer Discovery, Stefan Winter (10 minutes)=0Ahttp://t=
ools.ietf.org/html/draft-winter-dynamic-discovery=0A=C2=A0=0A10:50 - 11:00 =
AM RADIUS attributes for IPv6 Access Networks, Benoit Lourdelet (10 minutes=
)=0Ahttp://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access=0A=C2=A0=
=0A=0ASummary & Wrap-up =0A=0A=0A      
--0-1130777627-1236273676=:19441
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman, new york, times, serif;=
font-size:12pt"><DIV>Hi Benoit,</DIV>=0A<DIV>&nbsp; Were you in Minneapolis=
 last November?</DIV>=0A<DIV>&nbsp;</DIV>=0A<DIV>I think that draft-lourdel=
et-radext-rfc3162bis-02 is in line with what was agreed upon and what Berna=
rd had suggested that we do.</DIV>=0A<DIV>&nbsp;</DIV>=0A<DIV>I think that =
draft-lourdelet-radext-ipv6-access-00 is not.</DIV>=0A<DIV>&nbsp;</DIV>=0A<=
DIV>Merci,</DIV>=0A<DIV>&nbsp;</DIV>=0A<DIV>Behcet<BR></DIV>=0A<DIV style=
=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">=
<BR>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new yor=
k, times, serif"><FONT face=3DTahoma size=3D2>=0A<HR SIZE=3D1>=0A<B><SPAN s=
tyle=3D"FONT-WEIGHT: bold">From:</SPAN></B> Benoit Lourdelet (blourdel) &lt=
;[email-masked]&gt;<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN><=
/B> Behcet Sarikaya &lt;[email-masked]&gt;<BR><B><SPAN style=3D"FONT-WEI=
GHT: bold">Cc:</SPAN></B> [email-masked]; Bernard Aboba &lt;bernard=
[email-masked]&gt;<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN>=
</B> Thursday, March 5, 2009 11:03:00 AM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> RE: IETF 74 Agenda - Take Four<BR></FONT><BR>=0A<=
STYLE>=0A<!--=0A =0A _filtered {font-family:Calibri;=0Apanose-1:2 15 5 2 2 =
2 4 3 2 4;}=0A _filtered {font-family:Tahoma;=0Apanose-1:2 11 6 4 3 5 4 4 2=
 4;}=0A _filtered {font-family:Verdana;=0Apanose-1:2 11 6 4 3 5 4 4 2 4;}=
=0A =0Ap.MsoNormal, li.MsoNormal, div.MsoNormal=0A=09{margin:0in;=0Amargin-=
bottom:.0001pt;=0Afont-size:12.0pt;=0Afont-family:"Times New Roman", "serif=
";}=0Aa:link, span.MsoHyperlink=0A=09{=0Acolor:blue;=0Atext-decoration:unde=
rline;}=0Aa:visited, span.MsoHyperlinkFollowed=0A=09{=0Acolor:purple;=0Atex=
t-decoration:underline;}=0Ap=0A=09{=0A=0Amargin-right:0in;=0A=0Amargin-left=
:0in;=0Afont-size:12.0pt;=0Afont-family:"Times New Roman", "serif";}=0Ap.ec=
ecmsonormal, li.ececmsonormal, div.ececmsonormal=0A=09{=0A=0Amargin-right:0=
in;=0A=0Amargin-left:0in;=0Afont-size:12.0pt;=0Afont-family:"Times New Roma=
n", "serif";}=0Aspan.h1=0A=09{}=0Aspan.EmailStyle21=0A=09{=0Afont-family:"C=
alibri", "sans-serif";=0Acolor:#1F497D;}=0A.MsoChpDefault=0A=09{=0Afont-siz=
e:10.0pt;}=0A _filtered {=0Amargin:1.0in 1.0in 1.0in 1.0in;}=0Adiv.Section1=
=0A=09{}=0A-->=0A</STYLE>=0A=0A<DIV class=3DSection1>=0A<P class=3DMsoNorma=
l><SPAN style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri', '=
sans-serif'">Hello,</SPAN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-S=
IZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri', 'sans-serif'">&nbsp;</SP=
AN></P>=0A<P class=3DMsoNormal>FWI : draft-lourdelet-radext-rfc3162bis-02 m=
orphed into draft-lourdelet-radext-ipv6-access-00</P>=0A<P class=3DMsoNorma=
l>&nbsp;</P>=0A<P class=3DMsoNormal>Benoit </P>=0A<P class=3DMsoNormal><SPA=
N style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri', 'sans-s=
erif'">&nbsp;</SPAN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 1=
1pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri', 'sans-serif'">&nbsp;</SPAN></P=
>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FO=
NT-FAMILY: 'Calibri', 'sans-serif'">&nbsp;</SPAN></P>=0A<DIV>=0A<DIV style=
=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt =
solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PA=
DDING-TOP: 3pt; BORDER-BOTTOM: medium none">=0A<P class=3DMsoNormal><B><SPA=
N style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma', 'sans-serif'">From:</SPA=
N></B><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma', 'sans-serif'">=
 [email-masked] [mailto:[email-masked]] <B>On B=
ehalf Of </B>Behcet Sarikaya<BR><B>Sent:</B> Thursday, March 05, 2009 5:50 =
PM<BR><B>To:</B> Bernard Aboba; [email-masked]<BR><B>Subject:</B> R=
e: IETF 74 Agenda - Take Four</SPAN></P></DIV></DIV>=0A<P class=3DMsoNormal=
>&nbsp;</P>=0A<DIV>=0A<DIV>=0A<P class=3DMsoNormal>Hi Bernard,</P></DIV>=0A=
<DIV>=0A<P class=3DMsoNormal>&nbsp; Can you please squeeze a short presenta=
tion for draft-sarikaya-radext-prefix-authorization-02? We are revising the=
 draft in view of draft-lourdelet-radext-rfc3162bis-02.</P></DIV>=0A<DIV>=
=0A<P class=3DMsoNormal>&nbsp;</P></DIV>=0A<DIV>=0A<P class=3DMsoNormal>Reg=
ards,</P></DIV>=0A<DIV>=0A<P class=3DMsoNormal>&nbsp;</P></DIV>=0A<DIV>=0A<=
P class=3DMsoNormal>Behcet</P></DIV>=0A<DIV>=0A<P class=3DMsoNormal>&nbsp;<=
/P>=0A<DIV>=0A<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dc=
enter><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma', 'sans-serif'">=
=0A<HR align=3Dcenter width=3D"100%" SIZE=3D1>=0A</SPAN></DIV>=0A<P class=
=3DMsoNormal><B><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma', 'san=
s-serif'">From:</SPAN></B><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tah=
oma', 'sans-serif'"> Bernard Aboba &lt;[email-masked]&gt;<BR><B>=
To:</B> "[email-masked]" &lt;[email-masked]&gt;<BR><B>Sent:=
</B> Wednesday, March 4, 2009 4:11:02 PM<BR><B>Subject:</B> IETF 74 Agenda =
- Take Four<BR></SPAN><BR><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #444444; F=
ONT-FAMILY: 'Verdana', 'sans-serif'">At IETF 74, the RADEXT WG is currently=
 scheduled to meet on Friday, March 27,2009&nbsp; from 9 AM - 11:30 AM.&nbs=
p; Currently the Agenda is as follows:<BR>&nbsp;<BR>9 AM - 9:10 Preliminari=
es (10 minutes)<BR>&nbsp;&nbsp; Blue Sheets<BR>&nbsp;&nbsp; Note Takers<BR>=
&nbsp;&nbsp; Jabber Scribe<BR>&nbsp;&nbsp; Agenda bashing<BR>&nbsp;&nbsp; D=
ocument Status<BR>&nbsp;<BR>Documents completing IETF&nbsp;Last Call&nbsp;(=
20 minutes)<BR>&nbsp;<BR>9:10 - 9:20 AM&nbsp; RADIUS Authorization
 for NAS Management, David Nelson (10 minutes)<BR></SPAN><U><SPAN style=3D"=
FONT-SIZE: 10pt; COLOR: #0066cc; FONT-FAMILY: 'Verdana', 'sans-serif'">http=
://tools.ietf.org/html/draft-ietf-radext-management-authorization</SPAN></U=
><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 's=
ans-serif'"><BR>&nbsp;<BR>9:20 - 9:30 AM RADIUS Design Guidelines, Alan DeK=
ok (10 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-=
design" target=3D_blank rel=3Dnofollow><SPAN style=3D"COLOR: #0066cc">http:=
//tools.ietf.org/html/draft-ietf-radext-design</SPAN></A><BR>&nbsp;<BR>Docu=
ments that have completed RADEXT WG Last Call (50 minutes)</SPAN><BR>&nbsp;=
<BR><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdana',=
 'sans-serif'">9:30 AM =E2=80=93 9:40 AM Status-Server, Alan DeKok (10 minu=
tes)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-serv=
er" target=3D_blank rel=3Dnofollow><SPAN style=3D"COLOR:
 purple">http://tools.ietf.org/html/draft-ietf-radext-status-server</SPAN><=
/A><BR><BR>9:40 AM - 9:50 AM RADSEC, Stefan Winter (10 minutes)<BR><A href=
=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec" target=3D_blank re=
l=3Dnofollow><SPAN style=3D"COLOR: #0066cc">http://tools.ietf.org/html/draf=
t-ietf-radext-radsec</SPAN></A><BR>&nbsp;<BR>9:50 AM =E2=80=93&nbsp;10:00 A=
M Extended RADIUS Attributes, TBD (10 minutes)<BR>http://tools.ietf.org/htm=
l/draft-ietf-radext-extended-attributes<BR>&nbsp;<BR>10:00 AM - 10:20 AM RA=
DIUS Crypto-agility Requirements, David Nelson (20 minutes)<BR><A href=3D"h=
ttp://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements" ta=
rget=3D_blank rel=3Dnofollow><SPAN style=3D"COLOR: #0066cc">http://tools.ie=
tf.org/html/draft-ietf-radext-crypto-agility-requirements</SPAN></A></SPAN>=
</P>=0A<DIV>=0A<P class=3Dececmsonormal style=3D"BACKGROUND: white"><SPAN s=
tyle=3D"FONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 'sans-seri=
f'">&nbsp;<BR>Working Group Work Items (20 minutes)<BR>&nbsp;<BR>10:20 AM -=
 10:30 AM TCP Transport, Alan DeKok (10 minutes)<BR>http://tools.ietf.org/h=
tml/draft-ietf-radext-tcp-transport<BR><BR>10:30 AM - 10:40 AM New Tunnel-T=
ype Values, Abhishek Tiwari (10 minutes)<BR></SPAN><U><SPAN style=3D"FONT-S=
IZE: 10pt; COLOR: #0066cc; FONT-FAMILY: 'Verdana', 'sans-serif'">http://too=
ls.ietf.org/html/draft-ietf-radext-tunnel-type</SPAN></U><SPAN style=3D"FON=
T-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 'sans-serif'"><BR><BR=
>Individual Submissions (20 minutes)</SPAN></P>=0A<P class=3Dececmsonormal =
style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #444444;=
 FONT-FAMILY: 'Verdana', 'sans-serif'">&nbsp;</SPAN></P>=0A<P class=3Dececm=
sonormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZE: 10pt; COLOR:=
 #444444; FONT-FAMILY: 'Verdana', 'sans-serif'">10:40 AM - 10:50 AM&nbsp; N=
AI-based Dynamic Peer Discovery, Stefan Winter (10 minutes)</SPAN></P>=0A<P=
 class=3Dececmsonormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZE=
: 10pt; COLOR: #0068cf; FONT-FAMILY: 'Verdana', 'sans-serif'">http://tools.=
ietf.org/html/draft-winter-dynamic-discovery</SPAN></P>=0A<P class=3Dececms=
onormal style=3D"BACKGROUND: white">&nbsp;</P>=0A<P class=3Dececmsonormal s=
tyle=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: black; FO=
NT-FAMILY: 'Verdana', 'sans-serif'">10:50 - 11:00 AM <SPAN class=3Dh1>RADIU=
S attributes for IPv6 Access Networks</SPAN><STRONG><SPAN style=3D"FONT-FAM=
ILY: 'Verdana', 'sans-serif'">, </SPAN></STRONG>Benoit Lourdelet (10 minute=
s)</SPAN></P>=0A<P class=3Dececmsonormal style=3D"BACKGROUND: white"><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: #0068cf; FONT-FAMILY: 'Verdana', 'sans-ser=
if'">http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access</SPAN></=
P>=0A<P class=3Dececmsonormal style=3D"BACKGROUND: white">&nbsp;</P>=0A<P c=
lass=3Dececmsonormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZE: =
10pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 'sans-serif'"><BR>Summary &am=
p; Wrap-up</SPAN></P>=0A<TABLE class=3DMsoNormalTable style=3D"BORDER-RIGHT=
: medium none; BORDER-TOP: black 1pt solid; BORDER-LEFT: medium none; BORDE=
R-BOTTOM: medium none" cellPadding=3D0 border=3D1>=0A<TBODY>=0A<TR>=0A<TD s=
tyle=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0.75pt; BORDER-TOP: mediu=
m none; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; BORDER-LEFT: medium n=
one; PADDING-TOP: 0.75pt; BORDER-BOTTOM: medium none"></TD></TR></TBODY></T=
ABLE>=0A<P class=3Dececmsonormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMIL=
Y: 'Verdana', 'sans-serif'">&nbsp;</SPAN></P></DIV></DIV></DIV></DIV>=0A<P =
class=3DMsoNormal>&nbsp;</P></DIV></DIV></DIV></div><br>=0A=0A=0A=0A      <=
/body></html>
--0-1130777627-1236273676=:19441--

Delivery-date: Thu, 05 Mar 2009 17:03:40 +0000
Content-class: urn:content-classes:message
Subject: RE: IETF 74 Agenda - Take Four
Date: Thu, 5 Mar 2009 18:03:00 +0100
From: "Benoit Lourdelet (blourdel)" <[email-masked]>
To: "Behcet Sarikaya" <[email-masked]>
Cc: <[email-masked]>, "Bernard Aboba" <[email-masked]>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C99DB4.40D06618
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

------_=_NextPart_001_01C99DB4.40D06618
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

------_=_NextPart_001_01C99DB4.40D06618--

Envelope-to: [email-masked]
Delivery-date: Thu, 05 Mar 2009 16:51:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1236271826; bh=c4HJu6cG6nd7crWrYL2Y/9Rom7fD6csVHsZbaAelU+M=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=0T1XfPiJ3Ew9HfsGn3UrjDz2XDpWDO0P9CuHCqVvmKl0EcBnXBRlalcttPIspOH6DnlenAICpRkHtbAa/6lUDwPxp2vXOIVX5VxZJO+o3LXcli8XaBjovAvl1QADIZy/n1bfWYVG1ICqaa3G+Rd3rqvAsAZct/KdvMbBNm6Mco0=
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=YbPQ4ZfAAhEntHQ/mGRLka29plP77H6jO8GCyM7fVhklukWa0y3t76EBgtyMqPThdL1w675x28cYg0KAf4KK0jNZG7tVKWrcqA0okimrf58XM8BrKCDNCoM07+YJzNXsAEhw8RG223cWY/cU9E85Tg3TwER33iCo3YvvvphCNGM=;
Message-ID: <[email-masked]>
Date: Thu, 5 Mar 2009 08:50:26 -0800 (PST)
From: Behcet Sarikaya <[email-masked]>
Reply-To: Behcet Sarikaya <[email-masked]>
Subject: Re: IETF 74 Agenda - Take Four
To: Bernard Aboba <[email-masked]>, "[email-masked]" <[email-masked]>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1556768613-1236271826=:79201"

--0-1556768613-1236271826=:79201
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Bernard,=0A=C2=A0 Can you please squeeze a short presentation for draft-=
sarikaya-radext-prefix-authorization-02? We are revising the draft in view =
of draft-lourdelet-radext-rfc3162bis-02.=0A=0ARegards,=0A=0ABehcet=0A=0A=0A=
=0A=0A________________________________=0AFrom: Bernard Aboba <bernard_aboba=
@hotmail.com>=0ATo: "[email-masked]" <[email-masked]>=0ASen=
t: Wednesday, March 4, 2009 4:11:02 PM=0ASubject: IETF 74 Agenda - Take Fou=
r=0A=0AAt IETF 74, the RADEXT WG is currently scheduled to meet on Friday, =
March 27,2009=C2=A0 from 9 AM - 11:30 AM.=C2=A0 Currently the Agenda is as =
follows:=0A=C2=A0=0A9 AM - 9:10 Preliminaries (10 minutes)=0A=C2=A0=C2=A0 B=
lue Sheets=0A=C2=A0=C2=A0 Note Takers=0A=C2=A0=C2=A0 Jabber Scribe=0A=C2=A0=
=C2=A0 Agenda bashing=0A=C2=A0=C2=A0 Document Status=0A=C2=A0=0ADocuments c=
ompleting IETF=C2=A0Last Call=C2=A0(20 minutes)=0A=C2=A0=0A9:10 - 9:20 AM=
=C2=A0 RADIUS Authorization for NAS Management, David Nelson (10 minutes)=
=0Ahttp://tools.ietf.org/html/draft-ietf-radext-management-authorization=0A=
=C2=A0=0A9:20 - 9:30 AM RADIUS Design Guidelines, Alan DeKok (10 minutes)=
=0Ahttp://tools.ietf.org/html/draft-ietf-radext-design=0A=C2=A0=0ADocuments=
 that have completed RADEXT WG Last Call (50 minutes)=0A=C2=A0=0A9:30 AM =
=E2=80=93 9:40 AM Status-Server, Alan DeKok (10 minutes)=0Ahttp://tools.iet=
f.org/html/draft-ietf-radext-status-server=0A=0A9:40 AM - 9:50 AM RADSEC, S=
tefan Winter (10 minutes)=0Ahttp://tools.ietf.org/html/draft-ietf-radext-ra=
dsec=0A=C2=A0=0A9:50 AM =E2=80=93=C2=A010:00 AM Extended RADIUS Attributes,=
 TBD (10 minutes)=0Ahttp://tools.ietf.org/html/draft-ietf-radext-extended-a=
ttributes=0A=C2=A0=0A10:00 AM - 10:20 AM RADIUS Crypto-agility Requirements=
, David Nelson (20 minutes)=0Ahttp://tools.ietf.org/html/draft-ietf-radext-=
crypto-agility-requirements=0A=0A=C2=A0=0AWorking Group Work Items (20 minu=
tes)=0A=C2=A0=0A10:20 AM - 10:30 AM TCP Transport, Alan DeKok (10 minutes)=
=0Ahttp://tools.ietf.org/html/draft-ietf-radext-tcp-transport=0A=0A10:30 AM=
 - 10:40 AM New Tunnel-Type Values, Abhishek Tiwari (10 minutes)=0Ahttp://t=
ools.ietf.org/html/draft-ietf-radext-tunnel-type=0A=0AIndividual Submission=
s (20 minutes)=0A=C2=A0=0A10:40 AM - 10:50 AM=C2=A0 NAI-based Dynamic Peer =
Discovery, Stefan Winter (10 minutes)=0Ahttp://tools.ietf.org/html/draft-wi=
nter-dynamic-discovery=0A=C2=A0=0A10:50 - 11:00 AM RADIUS attributes for IP=
v6 Access Networks, Benoit Lourdelet (10 minutes)=0Ahttp://tools.ietf.org/h=
tml/draft-lourdelet-radext-ipv6-access=0A=C2=A0=0A=0ASummary & Wrap-up =0A=
=0A=0A      
--0-1556768613-1236271826=:79201
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman, new york, times, serif;=
font-size:12pt"><DIV>Hi Bernard,</DIV>=0A<DIV>&nbsp; Can you please squeeze=
 a short presentation for draft-sarikaya-radext-prefix-authorization-02? We=
 are revising the draft in view of draft-lourdelet-radext-rfc3162bis-02.</D=
IV>=0A<DIV>&nbsp;</DIV>=0A<DIV>Regards,</DIV>=0A<DIV>&nbsp;</DIV>=0A<DIV>Be=
hcet<BR></DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roma=
n, new york, times, serif"><BR>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMIL=
Y: times new roman, new york, times, serif"><FONT face=3DTahoma size=3D2>=
=0A<HR SIZE=3D1>=0A<B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> Be=
rnard Aboba &lt;[email-masked]&gt;<BR><B><SPAN style=3D"FONT-WEI=
GHT: bold">To:</SPAN></B> "[email-masked]" &lt;[email-masked]=
rg&gt;<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, =
March 4, 2009 4:11:02 PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Subject:</=
SPAN></B> IETF 74 Agenda - Take Four<BR></FONT><BR>=0A<STYLE>=0A.hmmessage =
P=0A{=0Amargin:0px;padding:0px;}=0Abody.hmmessage=0A{=0Afont-size:10pt;font=
-family:Verdana;}=0A</STYLE>=0A<SPAN style=3D"FONT-SIZE: 10pt; COLOR: #4444=
44; FONT-FAMILY: 'Verdana', 'sans-serif'">At IETF 74, the RADEXT WG is curr=
ently scheduled to meet on Friday, March 27,2009&nbsp; from 9 AM - 11:30 AM=
.&nbsp; Currently the Agenda is as follows:<BR>&nbsp;<BR>9 AM - 9:10 Prelim=
inaries (10 minutes)<BR>&nbsp;&nbsp; Blue Sheets<BR>&nbsp;&nbsp; Note Taker=
s<BR>&nbsp;&nbsp; Jabber Scribe<BR>&nbsp;&nbsp; Agenda bashing<BR>&nbsp;&nb=
sp; Document Status<BR>&nbsp;<BR>Documents completing IETF&nbsp;Last Call&n=
bsp;(20 minutes)<BR>&nbsp;<BR>9:10 - 9:20 AM&nbsp; RADIUS Authorization for=
 NAS Management, David Nelson (10 minutes)<BR></SPAN><U><SPAN style=3D"FONT=
-SIZE: 10pt; COLOR: #0066cc; FONT-FAMILY: 'Verdana', 'sans-serif'">http://t=
ools.ietf.org/html/draft-ietf-radext-management-authorization</SPAN></U><SP=
AN style=3D"FONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 'sans-=
serif'"><BR>&nbsp;<BR>9:20 - 9:30 AM RADIUS Design Guidelines, Alan DeKok (=
10 minutes)<BR><A
 href=3D"http://tools.ietf.org/html/draft-ietf-radext-design" target=3D_bla=
nk rel=3Dnofollow><SPAN style=3D"COLOR: #0066cc">http://tools.ietf.org/html=
/draft-ietf-radext-design</SPAN></A><BR>&nbsp;<BR>Documents that have compl=
eted RADEXT WG Last Call (50 minutes)</SPAN><BR><SPAN style=3D"FONT-SIZE: 1=
0pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 'sans-serif'"></SPAN>&nbsp;<BR=
><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 's=
ans-serif'"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'V=
erdana', 'sans-serif'">9:30 AM =E2=80=93 9:40 AM Status-Server, Alan DeKok =
(10 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-sta=
tus-server" target=3D_blank rel=3Dnofollow><SPAN style=3D"COLOR: purple">ht=
tp://tools.ietf.org/html/draft-ietf-radext-status-server</SPAN></A></SPAN><=
BR><BR>9:40 AM - 9:50 AM RADSEC, Stefan Winter (10 minutes)<BR><A href=3D"h=
ttp://tools.ietf.org/html/draft-ietf-radext-radsec" target=3D_blank rel=3Dn=
ofollow><SPAN style=3D"COLOR:
 #0066cc">http://tools.ietf.org/html/draft-ietf-radext-radsec</SPAN></A><BR=
>&nbsp;<BR>9:50 AM =E2=80=93&nbsp;10:00 AM Extended RADIUS Attributes, TBD =
(10 minutes)<BR>http://tools.ietf.org/html/draft-ietf-radext-extended-attri=
butes<BR>&nbsp;<BR>10:00 AM - 10:20 AM RADIUS Crypto-agility Requirements, =
David Nelson (20 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-ie=
tf-radext-crypto-agility-requirements" target=3D_blank rel=3Dnofollow><SPAN=
 style=3D"COLOR: #0066cc">http://tools.ietf.org/html/draft-ietf-radext-cryp=
to-agility-requirements</SPAN></A></SPAN><BR>=0A<DIV class=3DEC_EC_Section1=
>=0A<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"F=
ONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 'sans-serif'">&nbsp=
;</SPAN><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verda=
na', 'sans-serif'"><BR>Working Group Work Items (20 minutes)<BR>&nbsp;<BR>1=
0:20 AM - 10:30 AM TCP Transport, Alan DeKok (10 minutes)<BR>http://tools.i=
etf.org/html/draft-ietf-radext-tcp-transport<BR><BR>10:30 AM - 10:40 AM New=
 Tunnel-Type Values, Abhishek Tiwari (10 minutes)<BR></SPAN><U><SPAN style=
=3D"FONT-SIZE: 10pt; COLOR: #0066cc; FONT-FAMILY: 'Verdana', 'sans-serif'">=
http://tools.ietf.org/html/draft-ietf-radext-tunnel-type</SPAN></U><SPAN st=
yle=3D"FONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 'sans-serif=
'"><BR><BR>Individual Submissions (20 minutes)</SPAN></P>=0A<P class=3DEC_E=
C_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZE: 10pt; COL=
OR: #444444; FONT-FAMILY: 'Verdana', 'sans-serif'">&nbsp;</SPAN></P>=0A<P c=
lass=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZE=
: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdana', 'sans-serif'">10:40 AM - 10=
:50 AM&nbsp; NAI-based Dynamic Peer Discovery, Stefan Winter (10 minutes)</=
SPAN></P>=0A<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN st=
yle=3D"FONT-SIZE: 10pt; COLOR: #0068cf; FONT-FAMILY: 'Verdana', 'sans-serif=
'">http://tools.ietf.org/html/draft-winter-dynamic-discovery</SPAN></P>=0A<=
P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-S=
IZE: 10pt; COLOR: #0068cf; FONT-FAMILY: 'Verdana', 'sans-serif'"></SPAN>&nb=
sp;</P>=0A<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN styl=
e=3D"FONT-SIZE: 10pt; COLOR: #0068cf; FONT-FAMILY: 'Verdana', 'sans-serif'"=
><FONT color=3D#000000>10:50 - 11:00 AM <SPAN class=3Dh1>RADIUS attributes =
for IPv6 Access Networks<STRONG>, </STRONG></SPAN>Benoit Lourdelet (10 minu=
tes)</FONT></SPAN></P>=0A<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: wh=
ite"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #0068cf; FONT-FAMILY: 'Verdana'=
, 'sans-serif'">http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-acce=
ss</SPAN></P>=0A<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPA=
N style=3D"FONT-SIZE: 10pt; COLOR: #0068cf; FONT-FAMILY: 'Verdana', 'sans-s=
erif'"></SPAN>&nbsp;</P>=0A<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: =
white"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: #444444; FONT-FAMILY: 'Verdan=
a', 'sans-serif'"><BR>Summary &amp; Wrap-up</SPAN></P>=0A<TABLE class=3DEC_=
EC_MsoNormalTable style=3D"BORDER-RIGHT: medium none; BORDER-TOP: black 1pt=
 solid; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none" cellPadding=
=3D0 border=3D1>=0A<TBODY>=0A<TR>=0A<TD style=3D"BORDER-RIGHT: medium none;=
 PADDING-RIGHT: 0.75pt; BORDER-TOP: medium none; PADDING-LEFT: 0.75pt; PADD=
ING-BOTTOM: 0.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0.75pt; BORDER-B=
OTTOM: medium none"></TD></TR></TBODY></TABLE>=0A<P class=3DEC_EC_MsoNormal=
><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana', 'sans-serif'">&nbs=
p;</SPAN></P></DIV></DIV></DIV></div><br>=0A=0A      </body></html>
--0-1556768613-1236271826=:79201--

Delivery-date: Wed, 04 Mar 2009 22:12:01 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: IETF 74 Agenda - Take Four
Date: Wed, 4 Mar 2009 14:11:02 -0800

--_f7fa7a3e-0a37-43a1-8055-b92f63e64976_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

At IETF 74=2C the RADEXT WG is currently scheduled to meet on Friday=2C Mar=
ch 27=2C2009  from 9 AM - 11:30 AM.  Currently the Agenda is as follows:
=20
9 AM - 9:10 Preliminaries (10 minutes)
   Blue Sheets
   Note Takers
   Jabber Scribe
   Agenda bashing
   Document Status
=20
Documents completing IETF Last Call (20 minutes)
=20
9:10 - 9:20 AM  RADIUS Authorization for NAS Management=2C David Nelson (10=
 minutes)
http://tools.ietf.org/html/draft-ietf-radext-management-authorization
=20
9:20 - 9:30 AM RADIUS Design Guidelines=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design
=20
Documents that have completed RADEXT WG Last Call (50 minutes)

=20

9:30 AM =96 9:40 AM Status-Server=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

9:40 AM - 9:50 AM RADSEC=2C Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec
=20
9:50 AM =96 10:00 AM Extended RADIUS Attributes=2C TBD (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-extended-attributes
=20
10:00 AM - 10:20 AM RADIUS Crypto-agility Requirements=2C David Nelson (20 =
minutes)
http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements

=20
Working Group Work Items (20 minutes)
=20
10:20 AM - 10:30 AM TCP Transport=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:30 AM - 10:40 AM New Tunnel-Type Values=2C Abhishek Tiwari (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tunnel-type

Individual Submissions (20 minutes)
=20
10:40 AM - 10:50 AM  NAI-based Dynamic Peer Discovery=2C Stefan Winter (10 =
minutes)
http://tools.ietf.org/html/draft-winter-dynamic-discovery
=20
10:50 - 11:00 AM RADIUS attributes for IPv6 Access Networks=2C Benoit Lourd=
elet (10 minutes)
http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access
=20

Summary & Wrap-up

 =

--_f7fa7a3e-0a37-43a1-8055-b92f63e64976_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
<SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=
=2C'sans-serif'">At IETF 74=2C the RADEXT WG is currently scheduled to meet=
 on Friday=2C March 27=2C2009&nbsp=3B from 9 AM - 11:30 AM.&nbsp=3B Current=
ly the Agenda is as follows:<BR>&nbsp=3B<BR>9 AM - 9:10 Preliminaries (10 m=
inutes)<BR>&nbsp=3B&nbsp=3B Blue Sheets<BR>&nbsp=3B&nbsp=3B Note Takers<BR>=
&nbsp=3B&nbsp=3B Jabber Scribe<BR>&nbsp=3B&nbsp=3B Agenda bashing<BR>&nbsp=
=3B&nbsp=3B Document Status<BR>&nbsp=3B<BR>Documents completing IETF&nbsp=
=3BLast Call&nbsp=3B(20 minutes)<BR>&nbsp=3B<BR>9:10 - 9:20 AM&nbsp=3B RADI=
US Authorization for NAS Management=2C David Nelson (10 minutes)<BR></SPAN>=
<U><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #0066cc=3B FONT-FAMILY: 'Verdan=
a'=2C'sans-serif'"><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-=
management-authorization">http://tools.ietf.org/html/draft-ietf-radext-mana=
gement-authorization</A></SPAN></U><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR:=
 #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><BR>&nbsp=3B<BR>9:20 - 9=
:30 AM RADIUS Design Guidelines=2C Alan DeKok (10 minutes)<BR><A href=3D"ht=
tp://tools.ietf.org/html/draft-ietf-radext-design"><SPAN style=3D"COLOR: #0=
066cc">http://tools.ietf.org/html/draft-ietf-radext-design</SPAN></A><BR>&n=
bsp=3B<BR>Documents that have completed RADEXT WG Last Call (50 minutes)</S=
PAN><BR>
<SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=
=2C'sans-serif'"></SPAN>&nbsp=3B<BR>
<SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=
=2C'sans-serif'"><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-F=
AMILY: 'Verdana'=2C'sans-serif'">9:30 AM =96 9:40 AM Status-Server=2C Alan =
DeKok (10 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-rade=
xt-status-server"><SPAN style=3D"COLOR: purple">http://tools.ietf.org/html/=
draft-ietf-radext-status-server</SPAN></A></SPAN><BR>
<BR>9:40 AM - 9:50 AM RADSEC=2C Stefan Winter (10 minutes)<BR><A href=3D"ht=
tp://tools.ietf.org/html/draft-ietf-radext-radsec"><SPAN style=3D"COLOR: #0=
066cc">http://tools.ietf.org/html/draft-ietf-radext-radsec</SPAN></A><BR>&n=
bsp=3B<BR>9:50 AM =96&nbsp=3B10:00 AM Extended RADIUS Attributes=2C TBD (10=
 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-extend=
ed-attributes">http://tools.ietf.org/html/draft-ietf-radext-extended-attrib=
utes</A><BR>&nbsp=3B<BR>10:00 AM - 10:20 AM RADIUS Crypto-agility Requireme=
nts=2C David Nelson (20 minutes)<BR><A href=3D"http://tools.ietf.org/html/d=
raft-ietf-radext-crypto-agility-requirements"><SPAN style=3D"COLOR: #0066cc=
">http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements<=
/SPAN></A></SPAN><BR>
<DIV class=3DEC_EC_Section1>
<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-=
SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'">&nbs=
p=3B</SPAN><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY:=
 'Verdana'=2C'sans-serif'"><BR>Working Group Work Items (20 minutes)<BR>&nb=
sp=3B<BR>10:20 AM - 10:30 AM TCP Transport=2C Alan DeKok (10 minutes)<BR><A=
 href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport">http:/=
/tools.ietf.org/html/draft-ietf-radext-tcp-transport</A><BR><BR>10:30 AM - =
10:40 AM New Tunnel-Type Values=2C Abhishek Tiwari (10 minutes)<BR></SPAN><=
U><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #0066cc=3B FONT-FAMILY: 'Verdana=
'=2C'sans-serif'"><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-t=
unnel-type">http://tools.ietf.org/html/draft-ietf-radext-tunnel-type</A></S=
PAN></U><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'V=
erdana'=2C'sans-serif'"><BR><BR>Individual Submissions (20 minutes)</SPAN><=
/P>
<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-=
SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'">&nbs=
p=3B</SPAN></P>
<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-=
SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'">10:4=
0 AM - 10:50 AM&nbsp=3B NAI-based Dynamic Peer Discovery=2C Stefan Winter (=
10 minutes)</SPAN></P>
<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-=
SIZE: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><A h=
ref=3D"http://tools.ietf.org/html/draft-winter-dynamic-discovery">http://to=
ols.ietf.org/html/draft-winter-dynamic-discovery</A></SPAN></P>
<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-=
SIZE: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"></SP=
AN>&nbsp=3B</P>
<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-=
SIZE: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><FON=
T color=3D#000000>10:50 - 11:00 AM <SPAN class=3Dh1>RADIUS attributes for I=
Pv6 Access Networks<STRONG>=2C </STRONG></SPAN>Benoit Lourdelet (10 minutes=
)</FONT></SPAN></P>
<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-=
SIZE: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><A h=
ref=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access">http:=
//tools.ietf.org/html/draft-lourdelet-radext-ipv6-access</A></SPAN></P>
<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-=
SIZE: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"></SP=
AN>&nbsp=3B</P>
<P class=3DEC_EC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-=
SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><BR>=
Summary &amp=3B Wrap-up</SPAN></P>
<TABLE class=3DEC_EC_MsoNormalTable style=3D"BORDER-RIGHT: medium none=3B B=
ORDER-TOP: black 1pt solid=3B BORDER-LEFT: medium none=3B BORDER-BOTTOM: me=
dium none" cellPadding=3D0 border=3D1>
<TBODY>
<TR>
<TD style=3D"BORDER-RIGHT: medium none=3B PADDING-RIGHT: 0.75pt=3B BORDER-T=
OP: medium none=3B PADDING-LEFT: 0.75pt=3B PADDING-BOTTOM: 0.75pt=3B BORDER=
-LEFT: medium none=3B PADDING-TOP: 0.75pt=3B BORDER-BOTTOM: medium none"></=
TD></TR></TBODY></TABLE>
<P class=3DEC_EC_MsoNormal><SPAN style=3D"FONT-SIZE: 10pt=3B FONT-FAMILY: '=
Verdana'=2C'sans-serif'">&nbsp=3B</SPAN></P></DIV></body>
</html>=

--_f7fa7a3e-0a37-43a1-8055-b92f63e64976_--

Delivery-date: Wed, 04 Mar 2009 09:18:07 +0000
Content-class: urn:content-classes:message
Subject: RADIUS attributes for IPv6 access networks
Date: Wed, 4 Mar 2009 10:16:59 +0100
From: "Benoit Lourdelet (blourdel)" <[email-masked]>
To: <[email-masked]>
Cc: "Wojciech Dec (wdec)" <[email-masked]>, <[email-masked]>, "Benoit Lourdelet (blourdel)" <[email-masked]>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C99CAA.04B058F6
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

=20

=20

Following dicusssions at past IETF meetings, the solution to come with a
separate document to complete RFC3162 work was preferred.

=20

I'd appreciate your comment on the new draft that follows that approach.

=20

A new version of I-D, draft-lourdelet-radext-ipv6-access-00.txt has been
successfuly submitted by Benoit Lourdelet and posted to the IETF
repository.

=20

Filename:   draft-lourdelet-radext-ipv6-access

Revision:   00

Title:            RADIUS attributes for IPv6 Access Networks

Creation_date:    2009-03-03

WG ID:            Independent Submission

Number_of_pages: 8

=20

Abstract:

This document specifies new IPv6 attributes for RADIUS that complement
[RFC3162].  Its goal is to offer more IPv6 deployment options when
StateLess Address Auto Configuration (SLAAC) or DHCP are involved.

=20

Regards

=20

Benoit

------_=_NextPart_001_01C99CAA.04B058F6
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:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

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

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

<div class=3DSection1>

<p class=3DMsoNormal>Hello,<o:p></o:p></p>

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

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

<p class=3DMsoNormal>Following dicusssions at past IETF meetings, the =
solution to
come with a separate document to complete RFC3162 work was =
preferred.<o:p></o:p></p>

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

<p class=3DMsoNormal>I&#8217;d appreciate your comment on the new draft =
that
follows that approach.<o:p></o:p></p>

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

<p class=3DMsoPlainText>A new version of I-D,
draft-lourdelet-radext-ipv6-access-00.txt has been successfuly submitted =
by
Benoit Lourdelet and posted to the IETF repository.<o:p></o:p></p>

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

<p class=3DMsoPlainText>Filename:&nbsp;&nbsp;  =
draft-lourdelet-radext-ipv6-access<o:p></o:p></p>

<p class=3DMsoPlainText>Revision:&nbsp;&nbsp;  00<o:p></o:p></p>

<p =
class=3DMsoPlainText>Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
RADIUS attributes for IPv6 Access Networks<o:p></o:p></p>

<p class=3DMsoPlainText>Creation_date:&nbsp;&nbsp;&nbsp;  =
2009-03-03<o:p></o:p></p>

<p class=3DMsoPlainText>WG =
ID:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Independent Submission<o:p></o:p></p>

<p class=3DMsoPlainText>Number_of_pages: 8<o:p></o:p></p>

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

<p class=3DMsoPlainText>Abstract:<o:p></o:p></p>

<p class=3DMsoPlainText>This document specifies new IPv6 attributes for =
RADIUS that
complement [RFC3162].&nbsp; Its goal is to offer more IPv6 deployment =
options
when StateLess Address Auto Configuration (SLAAC) or DHCP are =
involved.<o:p></o:p></p>

<p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></p>

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C99CAA.04B058F6--

Delivery-date: Wed, 04 Mar 2009 07:43:04 +0000
Date: Wed, 04 Mar 2009 08:42:06 +0100
From: Stefan Winter <[email-masked]>
To: "Joseph Salowey (jsalowey)" <[email-masked]>
CC: [email-masked]
Subject: Re: Issue 282: cert validation, proposed text

Hi,

>>        *  Certificate validation MUST include the 
>> verification rules as
>>           per [RFC5280].  If an SRV entry is present in the 
>> certificate
>>           and dynamic discovery based on DNS is used, the SRV entry
>>           SHOULD be validated. refence x.y.z here.
>>
>>     
> [Joe] Where is the SRV entry present in the certificate?  What does it look like? What is the value in the certificate validated against?  
>   

Right, sorry, I should have expanded on "reference x.y.z" :-) This is
about RFC4985: "Internet X.509 Public Key Infrastructure - Subject
Alternative Name for Expression of Service Name".

It defines a subjectAltName - otherName that's supposed to contain the
SRV record. I understood that so far, checking this is not in popular
TLS implementations yet, but it looks useful and deserves to be
mentioned IMHO. I'll update the reference in the draft.

> [Joe] I would suggest specifying a format for interop here.  You might want to take a look at 
> http://tools.ietf.org/html/draft-ietf-syslog-transport-tls-14 which is somewhat similar and has some text on fingerprint matching.  
>   

Looks good, I'll add corresponding text to the next version of the draft.

>>        *  Peer validation always includes a check on whether the DNS
>>           name or the IP address of the server that is 
>> contacted matches
>>           its certificate.  DNS names and IP addresses can be 
>> contained
>>           in the Common Name (CN) or subjectAltName entries.  For
>>           verification, only one these entries is to be 
>> considered.  The
>>           following precedence applies: for DNS name validation,
>>           subjectAltName:DNS has precedence over CN; for IP address
>>           validation, subjectAltName:iPAddr has precedence over CN.
>>
>>     
> [Joe] In the syslog document referenced above we made it mandatory to support subjectAltName:DNSname matching.   Other places for the identity are allowed.  
>   

Ok, thanks for the pointer. That text looks good, and I might be tempted
to copy&paste from it :-). Just one question on it: if both a
subjectAltName:DNS and a CN are present, what if they differ? Which of
the entries gets precedence? Or is a match of any of the entries good
enough? My text emerged due to the impression that CN is regarded as
deprecated when subjectAltName:DNS is present, and consequently gives
subjectAltName:DNS precedence.

>>        *  Implementations SHOULD allow to configure a set of 
>> acceptable
>>           values for subjectAltName:URI.
>>     
> [Joe] What does the URI look like?  
>   

This is not constrained and defined by the users of the spec. As an
example, for the eduroam roaming consortium, we use a URL containing a
URN (due to subjectAltName:URI constraints, we can't use a URN directly):

The identity provider for the domain restena.lu has, for example:

URI:https://registry.edugain.org/resolver?urn=urn:geant:eduroam:component:idp:Europe:RESTENA:restena.lu

This enables checking on "urn:geant:eduroam:component:" as authorisation check. Plus, putting this URL into a browser will yield the registration data from the authoritative URN registry.

Other roaming consortia can define their own acceptable URI schemes.

Greetings,

Stefan Winter

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

Tel: +352 424409 1
Fax: +352 422473

Delivery-date: Wed, 04 Mar 2009 03:56:57 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: WG Last Call on RADSEC
Date: Tue, 3 Mar 2009 19:56:39 -0800

--_5c957688-1bb3-4c89-8d6e-52e6843e6d3d_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is an announcement of RADEXT WG last call on the RADSEC specification=
=2C prior to sending this document on to the IESG for publication as an Exp=
erimental RFC.  The document is available for inspection here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-03.txt

RADEXT WG last call will last until March 30=2C 2009.  Please send comments=
 to the RADEXT WG mailing list using the format described in the RADEXT Iss=
ues list (http://www.drizzle.com/~aboba/RADEXT/). =20

--_5c957688-1bb3-4c89-8d6e-52e6843e6d3d_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
This is an announcement of RADEXT WG last call on the RADSEC specification=
=2C prior to sending this document on to the IESG for publication as an Exp=
erimental RFC.&nbsp=3B The document is available for inspection here:<br>ht=
tp://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-03.txt<br><br>RA=
DEXT WG last call will last until March 30=2C 2009.&nbsp=3B Please send com=
ments to the RADEXT WG mailing list using the format described in the RADEX=
T Issues list (http://www.drizzle.com/~aboba/RADEXT/).&nbsp=3B <br><br><br>=
<br><table style=3D"border-top: 1px solid black=3B font-weight: bold=3B fon=
t-family: 'Segoe UI'=2CTahoma=2Csan-serif=3B"><tbody><tr><td><br></td></tr>=
</tbody></table></body>
</html>=

--_5c957688-1bb3-4c89-8d6e-52e6843e6d3d_--

Delivery-date: Wed, 04 Mar 2009 03:51:52 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: Review requested:  NAI-based Peer Discovery Document
Date: Tue, 3 Mar 2009 19:51:07 -0800

--_d7104eca-be78-41f1-986c-848fe84749e4_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is a call for review of the document "NAI-based Peer Discovery".  The =
document is available for review here:
http://www.ietf.org/internet-drafts/draft-winter-dynamic-discovery-00.txt

This document=2C which includes material formerly included in the RADSEC sp=
ecification=2C has been separated out into its own document.=20

--_d7104eca-be78-41f1-986c-848fe84749e4_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
This is a call for review of the document "NAI-based Peer Discovery".&nbsp=
=3B The document is available for review here:<br>http://www.ietf.org/inter=
net-drafts/draft-winter-dynamic-discovery-00.txt<br><br>This document=2C wh=
ich includes material formerly included in the RADSEC specification=2C has =
been separated out into its own document. <br><table style=3D"border-top: 1=
px solid black=3B font-weight: bold=3B font-family: 'Segoe UI'=2CTahoma=2Cs=
an-serif=3B"><tbody><tr><td><a href=3D"http://im.live.com/Messenger/IM/Home=
/?source=3DEML_WLHM_GreaterGood" style=3D"font-size: 9pt=3B color: rgb(1=2C=
 132=2C 203)=3B text-decoration: none=3B"><span style=3D"padding: 0px 24px=
=3B font-size: 8pt=3B color: rgb(63=2C 181=2C 85)=3B text-decoration: under=
line=3B"></span></a><br></td></tr></tbody></table></body>
</html>=

--_d7104eca-be78-41f1-986c-848fe84749e4_--

Delivery-date: Wed, 04 Mar 2009 00:48:53 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: IETF 74 Agenda - Take Three
Date: Tue, 3 Mar 2009 16:47:53 -0800

--_f2add505-d3f7-4bd2-9ad2-4854c0570f41_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

At IETF 74=2C the RADEXT WG is currently scheduled to meet on March 23=2C20=
09  from 9 AM - 11:30 AM.  Currently the Agenda is as follows:
=20
9 AM - 9:10 Preliminaries (10 minutes)
   Blue Sheets
   Note Takers
   Jabber Scribe
   Agenda bashing
   Document Status
=20
Documents completing IESG Evaluation (10 minutes)
=20
9:10 - 9:20 AM  RADIUS Authorization for NAS Management=2C David Nelson (10=
 minutes)
http://tools.ietf.org/html/draft-ietf-radext-management-authorization

Documents in Last Look (10 minutes)
=20
9:20 - 9:30 AM RADIUS Design Guidelines=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design
=20
Documents that have completed RADEXT WG Last Call (40 minutes)

9:30 AM - 9:40 AM RADSEC=2C Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec
=20
9:40 AM =96 9:50 AM Extended RADIUS Attributes=2C TBD (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-extended-attributes
=20
9:50 AM - 10:00 AM RADIUS Crypto-agility Requirements=2C David Nelson (10 m=
inutes)
http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements

=20
10:00 AM =96 10:10 AM Status-Server=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server
 =20
Working Group Work Items (30 minutes)
=20
10:10 AM - 10:20 AM TCP Transport=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:20 AM - 10:25 AM New Tunnel-Type Values=2C Abhishek Tiwari (5 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tunnel-type

Individual Submissions
=20
10:25 AM - 10:35 AM  NAI-based Dynamic Peer Discovery=2C Stefan Winter (10 =
minutes)
http://tools.ietf.org/html/draft-winter-dynamic-discovery
=20
10:35 - 10:45 AM RADIUS attributes for IPv6 Access Networks=2C Benoit Lourd=
elet (10 minutes)
http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access
=20

Summary & Wrap-up
=20

 =

--_f2add505-d3f7-4bd2-9ad2-4854c0570f41_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
<SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=
=2C'sans-serif'">At IETF 74=2C the RADEXT WG is currently scheduled to meet=
 on March 23=2C2009&nbsp=3B from 9 AM - 11:30 AM.&nbsp=3B Currently the Age=
nda is as follows:<BR>&nbsp=3B<BR>9 AM - 9:10 Preliminaries (10 minutes)<BR=
>&nbsp=3B&nbsp=3B Blue Sheets<BR>&nbsp=3B&nbsp=3B Note Takers<BR>&nbsp=3B&n=
bsp=3B Jabber Scribe<BR>&nbsp=3B&nbsp=3B Agenda bashing<BR>&nbsp=3B&nbsp=3B=
 Document Status<BR>&nbsp=3B<BR>Documents completing IESG Evaluation (10 mi=
nutes)<BR>&nbsp=3B<BR>9:10 - 9:20 AM&nbsp=3B RADIUS Authorization for NAS M=
anagement=2C David Nelson (10 minutes)<BR></SPAN><U><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #0066cc=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><A href=
=3D"http://tools.ietf.org/html/draft-ietf-radext-management-authorization">=
http://tools.ietf.org/html/draft-ietf-radext-management-authorization</A></=
SPAN></U><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: '=
Verdana'=2C'sans-serif'"><BR><BR>Documents in Last Look (10 minutes)<BR>&nb=
sp=3B<BR>9:20 - 9:30 AM RADIUS Design Guidelines=2C Alan DeKok (10 minutes)=
<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-design"><SPAN s=
tyle=3D"COLOR: #0066cc">http://tools.ietf.org/html/draft-ietf-radext-design=
</SPAN></A><BR>&nbsp=3B<BR>Documents that have completed RADEXT WG Last Cal=
l (40 minutes)<BR><BR>9:30 AM - 9:40 AM RADSEC=2C Stefan Winter (10 minutes=
)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec"><SPAN =
style=3D"COLOR: #0066cc">http://tools.ietf.org/html/draft-ietf-radext-radse=
c</SPAN></A><BR>&nbsp=3B<BR>9:40 AM =96&nbsp=3B9:50 AM Extended RADIUS Attr=
ibutes=2C TBD (10 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-i=
etf-radext-extended-attributes">http://tools.ietf.org/html/draft-ietf-radex=
t-extended-attributes</A><BR>&nbsp=3B<BR>9:50&nbsp=3BAM - 10:00 AM RADIUS C=
rypto-agility Requirements=2C David Nelson (10 minutes)<BR><A href=3D"http:=
//tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements"><SPAN =
style=3D"COLOR: #0066cc">http://tools.ietf.org/html/draft-ietf-radext-crypt=
o-agility-requirements</SPAN></A></SPAN><BR>
<DIV class=3DEC_Section1>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'">&nbsp=
=3B</SPAN></P>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'">10:00 A=
M =96 10:10 AM Status-Server=2C Alan DeKok (10 minutes)<BR><A href=3D"http:=
//tools.ietf.org/html/draft-ietf-radext-status-server"><SPAN style=3D"COLOR=
: purple">http://tools.ietf.org/html/draft-ietf-radext-status-server</SPAN>=
</A><BR>&nbsp=3B&nbsp=3B<BR>Working Group Work Items (30 minutes)<BR>&nbsp=
=3B<BR>10:10 AM - 10:20 AM TCP Transport=2C Alan DeKok (10 minutes)<BR><A h=
ref=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport">http://t=
ools.ietf.org/html/draft-ietf-radext-tcp-transport</A><BR><BR>10:20 AM - 10=
:25 AM New Tunnel-Type Values=2C Abhishek Tiwari (5 minutes)<BR></SPAN><U><=
SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #0066cc=3B FONT-FAMILY: 'Verdana'=
=2C'sans-serif'"><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-tu=
nnel-type">http://tools.ietf.org/html/draft-ietf-radext-tunnel-type</A></SP=
AN></U><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Ve=
rdana'=2C'sans-serif'"><BR><BR>Individual Submissions</SPAN></P>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'">&nbsp=
=3B</SPAN></P>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'">10:25 A=
M - 10:35 AM&nbsp=3B NAI-based Dynamic Peer Discovery=2C Stefan Winter (10 =
minutes)</SPAN></P>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><A href=
=3D"http://tools.ietf.org/html/draft-winter-dynamic-discovery">http://tools=
.ietf.org/html/draft-winter-dynamic-discovery</A></SPAN></P>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"></SPAN>=
&nbsp=3B</P>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><FONT c=
olor=3D#000000>10:35 - 10:45 AM <SPAN class=3Dh1>RADIUS attributes for IPv6=
 Access Networks<STRONG>=2C </STRONG></SPAN>Benoit Lourdelet (10 minutes)</=
FONT></SPAN></P>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><A href=
=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access">http://t=
ools.ietf.org/html/draft-lourdelet-radext-ipv6-access</A></SPAN></P>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #0068cf=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"></SPAN>=
&nbsp=3B</P>
<P class=3DEC_MsoNormal style=3D"BACKGROUND: white"><SPAN style=3D"FONT-SIZ=
E: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'"><BR>Sum=
mary &amp=3B Wrap-up</SPAN></P>
<P class=3DEC_MsoNormal style=3D"MARGIN-BOTTOM: 10pt">&nbsp=3B</P>
<TABLE class=3DEC_MsoNormalTable style=3D"BORDER-RIGHT: medium none=3B BORD=
ER-TOP: black 1pt solid=3B BORDER-LEFT: medium none=3B BORDER-BOTTOM: mediu=
m none" cellPadding=3D0 border=3D1>
<TBODY>
<TR>
<TD style=3D"BORDER-RIGHT: medium none=3B PADDING-RIGHT: 0.75pt=3B BORDER-T=
OP: medium none=3B PADDING-LEFT: 0.75pt=3B PADDING-BOTTOM: 0.75pt=3B BORDER=
-LEFT: medium none=3B PADDING-TOP: 0.75pt=3B BORDER-BOTTOM: medium none"></=
TD></TR></TBODY></TABLE>
<P class=3DEC_MsoNormal><SPAN style=3D"FONT-SIZE: 10pt=3B FONT-FAMILY: 'Ver=
dana'=2C'sans-serif'">&nbsp=3B</SPAN></P></DIV></body>
</html>=

--_f2add505-d3f7-4bd2-9ad2-4854c0570f41_--

Delivery-date: Tue, 03 Mar 2009 19:18:23 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: IETF 74 Agenda - Take Two
Date: Tue, 3 Mar 2009 11:17:38 -0800

--_b68a5edd-3c7d-4200-84fe-4439f9092c56_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

At IETF 74=2C the RADEXT WG is currently scheduled to meet on March 23=2C20=
09  from 9 AM - 11:30 AM.  Currently the Agenda is as follows:
=20
9 AM - 9:10 Preliminaries (10 minutes)
   Blue Sheets
   Note Takers
   Jabber Scribe
   Agenda bashing
   Document Status
=20
Documents completing IESG Evaluation (10 minutes)
=20
9:10 - 9:20 AM  RADIUS Authorization for NAS Management=2C David Nelson (10=
 minutes)
http://tools.ietf.org/html/draft-ietf-radext-management-authorization

Documents in Last Look (10 minutes)
=20
9:20 - 9:30 AM RADIUS Design Guidelines=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design
=20
Documents that have completed RADEXT WG Last Call (40 minutes)

9:30 AM - 9:40 AM RADSEC=2C Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec
=20
9:40 AM =96 9:50 AM Extended RADIUS Attributes=2C TBD (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-extended-attributes
=20
9:50 AM - 10:00 AM RADIUS Crypto-agility Requirements=2C David Nelson (10 m=
inutes)
http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements
=20
10:00 AM =96 10:10 AM Status-Server=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server
 =20
Working Group Work Items (30 minutes)
=20
10:10 AM - 10:20 AM TCP Transport=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:20 AM - 10:25 AM New Tunnel-Type Values=2C Abhishek Tiwari (5 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tunnel-type

Individual Submissions
=20
10:25 AM - 10:35 AM  NAI-based Dynamic Peer Discovery=2C Stefan Winter (10 =
minutes)
http://tools.ietf.org/html/draft-winter-dynamic-discovery

Summary & Wrap-up
=20

--_b68a5edd-3c7d-4200-84fe-4439f9092c56_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
<P class=3DMsoNormal style=3D"BACKGROUND: white=3B MARGIN: 0in 0in 0pt=3B L=
INE-HEIGHT: normal"><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FON=
T-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-fareast-font-family: 'Times New R=
oman'=3B mso-bidi-font-family: 'Segoe UI'">At IETF 74=2C the RADEXT WG is c=
urrently scheduled to meet on March 23=2C2009&nbsp=3B from 9 AM - 11:30 AM.=
<SPAN style=3D"mso-spacerun: yes">&nbsp=3B </SPAN>Currently the Agenda is a=
s follows:<BR>&nbsp=3B<BR>9 AM - 9:10 Preliminaries (10 minutes)<BR>&nbsp=
=3B&nbsp=3B Blue Sheets<BR>&nbsp=3B&nbsp=3B Note Takers<BR>&nbsp=3B&nbsp=3B=
 Jabber Scribe<BR>&nbsp=3B&nbsp=3B Agenda bashing<BR>&nbsp=3B&nbsp=3B Docum=
ent Status<BR>&nbsp=3B<BR>Documents completing IESG Evaluation (10 minutes)=
<BR>&nbsp=3B<BR>9:10 - 9:20 AM&nbsp=3B RADIUS Authorization for NAS Managem=
ent=2C David Nelson (10 minutes)<BR></SPAN><U><SPAN style=3D"FONT-SIZE: 10p=
t=3B COLOR: #0066cc=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-fareast=
-font-family: 'Times New Roman'=3B mso-bidi-font-family: 'Segoe UI'"><A hre=
f=3D"http://tools.ietf.org/html/draft-ietf-radext-management-authorization"=
>http://tools.ietf.org/html/draft-ietf-radext-management-authorization</A><=
/SPAN></U><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: =
'Verdana'=2C'sans-serif'=3B mso-fareast-font-family: 'Times New Roman'=3B m=
so-bidi-font-family: 'Segoe UI'"><BR><BR>Documents in Last Look (10 minutes=
)<BR>&nbsp=3B<BR>9:20 - 9:30 AM RADIUS Design Guidelines=2C Alan DeKok (10 =
minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-design"=
><SPAN style=3D"COLOR: #0066cc">http://tools.ietf.org/html/draft-ietf-radex=
t-design</SPAN></A><BR>&nbsp=3B<BR>Documents that have completed RADEXT WG =
Last Call (40 minutes)<BR><BR>9:30 AM - 9:40 AM RADSEC=2C Stefan Winter (10=
 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec=
"><SPAN style=3D"COLOR: #0066cc">http://tools.ietf.org/html/draft-ietf-rade=
xt-radsec</SPAN></A><BR>&nbsp=3B<BR>9:40 AM =96&nbsp=3B9:50 AM Extended RAD=
IUS Attributes=2C TBD (10 minutes)<BR><A href=3D"http://tools.ietf.org/html=
/draft-ietf-radext-extended-attributes"><SPAN style=3D"COLOR: blue">http://=
tools.ietf.org/html/draft-ietf-radext-extended-attributes</SPAN></A><BR>&nb=
sp=3B<BR>9:50&nbsp=3BAM - 10:00 AM RADIUS Crypto-agility Requirements=2C Da=
vid Nelson (10 minutes)<BR><A href=3D"http://tools.ietf.org/html/draft-ietf=
-radext-crypto-agility-requirements"><SPAN style=3D"COLOR: #0066cc">http://=
tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements</SPAN></A=
><?xml:namespace prefix =3D o ns =3D "urn:schemas-microsoft-com:office:offi=
ce" /><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"BACKGROUND: white=3B MARGIN: 0in 0in 0pt=3B L=
INE-HEIGHT: normal"><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FON=
T-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-fareast-font-family: 'Times New R=
oman'=3B mso-bidi-font-family: 'Segoe UI'"><o:p>&nbsp=3B</o:p></SPAN></P>
<P class=3DMsoNormal style=3D"BACKGROUND: white=3B MARGIN: 0in 0in 0pt=3B L=
INE-HEIGHT: normal"><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FON=
T-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-fareast-font-family: 'Times New R=
oman'=3B mso-bidi-font-family: 'Segoe UI'">10:00 AM =96 10:10 AM Status-Ser=
ver=2C Alan DeKok (10 minutes)<BR><A href=3D"http://tools.ietf.org/html/dra=
ft-ietf-radext-status-server"><SPAN style=3D"COLOR: purple">http://tools.ie=
tf.org/html/draft-ietf-radext-status-server</SPAN></A><BR>&nbsp=3B&nbsp=3B<=
BR>Working Group Work Items (30 minutes)<BR>&nbsp=3B<BR>10:10 AM - 10:20 AM=
 TCP Transport=2C Alan DeKok (10 minutes)<BR><A href=3D"http://tools.ietf.o=
rg/html/draft-ietf-radext-tcp-transport">http://tools.ietf.org/html/draft-i=
etf-radext-tcp-transport</A><BR><BR>10:20 AM - 10:25 AM New Tunnel-Type Val=
ues=2C Abhishek Tiwari (5 minutes)<BR></SPAN><U><SPAN style=3D"FONT-SIZE: 1=
0pt=3B COLOR: #0066cc=3B FONT-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-farea=
st-font-family: 'Times New Roman'=3B mso-bidi-font-family: 'Segoe UI'"><A h=
ref=3D"http://tools.ietf.org/html/draft-ietf-radext-tunnel-type"><SPAN styl=
e=3D"COLOR: blue">http://tools.ietf.org/html/draft-ietf-radext-tunnel-type<=
/SPAN></A></SPAN></U><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FO=
NT-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-fareast-font-family: 'Times New =
Roman'=3B mso-bidi-font-family: 'Segoe UI'"><BR><BR>Individual Submissions<=
o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"BACKGROUND: white=3B MARGIN: 0in 0in 0pt=3B L=
INE-HEIGHT: normal"><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FON=
T-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-fareast-font-family: 'Times New R=
oman'=3B mso-bidi-font-family: 'Segoe UI'">&nbsp=3B<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"BACKGROUND: white=3B MARGIN: 0in 0in 0pt=3B L=
INE-HEIGHT: normal"><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FON=
T-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-fareast-font-family: 'Times New R=
oman'=3B mso-bidi-font-family: 'Segoe UI'">10:25 AM - 10:35 AM&nbsp=3B NAI-=
based Dynamic Peer Discovery=2C Stefan Winter (10 minutes)<o:p></o:p></SPAN=
></P>
<P class=3DMsoNormal style=3D"BACKGROUND: white=3B MARGIN: 0in 0in 0pt=3B L=
INE-HEIGHT: normal"><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #0068cf=3B FON=
T-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-fareast-font-family: 'Times New R=
oman'=3B mso-bidi-font-family: 'Segoe UI'"><A href=3D"http://tools.ietf.org=
/html/draft-winter-dynamic-discovery"><SPAN style=3D"COLOR: blue">http://to=
ols.ietf.org/html/draft-winter-dynamic-discovery</SPAN></A></SPAN><SPAN sty=
le=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FONT-FAMILY: 'Verdana'=2C'sans-s=
erif'=3B mso-fareast-font-family: 'Times New Roman'=3B mso-bidi-font-family=
: 'Segoe UI'"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"BACKGROUND: white=3B MARGIN: 0in 0in 0pt=3B L=
INE-HEIGHT: normal"><SPAN style=3D"FONT-SIZE: 10pt=3B COLOR: #444444=3B FON=
T-FAMILY: 'Verdana'=2C'sans-serif'=3B mso-fareast-font-family: 'Times New R=
oman'=3B mso-bidi-font-family: 'Segoe UI'"><BR>Summary &amp=3B Wrap-up<o:p>=
</o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 10pt"><o:p><FONT color=3D#000=
000>&nbsp=3B</FONT></o:p></P>

<P>
<TABLE style=3D"BORDER-TOP: black 1px solid=3B FONT-WEIGHT: bold=3B FONT-FA=
MILY: 'Segoe UI'=2CTahoma=2Csan-serif">
<TBODY>
<TR>
<TD><BR></TD></TR></TBODY></TABLE><BR></P></body>
</html>=

--_b68a5edd-3c7d-4200-84fe-4439f9092c56_--

Delivery-date: Tue, 03 Mar 2009 18:04:34 +0000
Date: Tue, 03 Mar 2009 19:02:54 +0100
From: Alan DeKok <[email-masked]>
To: Bernard Aboba <[email-masked]>
CC: "[email-masked]" <[email-masked]>
Subject: Re: Comments on  "RADIUS Design Guidelines" document

Bernard Aboba wrote:
>> > OK. The question still remains, though. If an attribute is only used in
>> > Accounting-Request packets, does the argument against complex
>> > attributes still apply?
>>
>> My preference would be to say yes, especially where the contents of
>> that attribute are interpreted by *later* policies on the server.
> 
> Now that we have RFC 5176, accounting data can be kept as "state" that is
> later used to construct CoA/Disconnect-Requests.  Is this what you mean?

  No.

  I mean billing based on information in the accounting packets, and
policies based on billing && the state of the user account.

  e.g. Some NAS vendors "helpfully" put traffic usage into a VSA, as a
set of text fields: "476 529 8836734 347474", as "packets in/out, octets
in/out".

  The fact that this is obviously stupid is beside the point.  *Any*
accounting data that is buried inside of a sub-field will magically
become critical information that some company needs to run their billing
engine.

  Alan DeKok.

Delivery-date: Tue, 03 Mar 2009 16:44:01 +0000
Content-class: urn:content-classes:message
Subject: RE: Issue 282: cert validation, proposed text
Date: Tue, 3 Mar 2009 08:43:17 -0800
From: "Joseph Salowey (jsalowey)" <[email-masked]>
To: "Stefan Winter" <[email-masked]>
Cc: <[email-masked]>

Hi Stefan,

Some comments below.=20

> -----Original Message-----
> From: Stefan Winter [mailto:[email-masked]]=20
> Sent: Wednesday, February 11, 2009 1:13 AM
> To: Joseph Salowey (jsalowey)
> Cc: [email-masked]
> Subject: Issue 282: cert validation, proposed text
>=20
> Hi,
>=20
> > 2.  I think the certificate handling and authorization=20
> section needs=20
> > to be more specific for supporting mandatory to implement options.
> > Currently, the document implicitly requires trust root based=20
> > authorization where all certs issued by a given trust root are=20
> > authorized.  Some more specific rules are discussed in an=20
> informative=20
> > section.  I believe some of this needs to be normative and more=20
> > specific in order to have interoperable implementations. =20
> This should=20
> > also be discussed in the security considerations.
> >  =20
>=20
> Section 2.2 now reads:
>=20
> 2.2.  Connection Setup
>=20
>    RadSec nodes
>=20
>    1.  establish TCP connections as per=20
> [I-D.dekok-radext-tcp-transport]
>=20
>    2.  negotiate TLS sessions according to [RFC5246] or its=20
> predecessor
>        TLS 1.1.  The following restrictions apply:
>=20
>        *  The authentication MUST be mutual, i.e. both the=20
> RadSec server
>           and the RadSec client authenticate each other.
>=20
>        *  The client MUST NOT negotiate cipher suites which=20
> only provide
>           integrity protection.
>=20
>        *  The TLS session MAY use mutual PSKs for connection setup.
>=20
>        *  The cipher suite TLS_RSA_WITH_3DES_EDE_CBC_SHA MUST be
>           supported.
>=20
>        *  The cipher suites TLS_RSA_WITH_AES_128_CBC_SHA and
>           TLS_RSA_WITH_RC4_128_SHA SHOULD be supported. (see=20
> Section 3.2
>           (1) )
>=20
>    3.  If TLS is used in an X.509 certificate based operation=20
> mode, the
>        following list of certificate validation options applies:
>=20
>        *  Implementations MUST allow to configure a list of acceptable
>           Certification Authorities for incoming connections.
>=20
>        *  Certificate validation MUST include the=20
> verification rules as
>           per [RFC5280].  If an SRV entry is present in the=20
> certificate
>           and dynamic discovery based on DNS is used, the SRV entry
>           SHOULD be validated. refence x.y.z here.
>=20
[Joe] Where is the SRV entry present in the certificate?  What does it =
look like? What is the value in the certificate validated against? =20

>        *  Implementations SHOULD indicate their acceptable=20
> Certification
>           Authorities as per section 7.4.4 (server side) and x.y.z
>           ["Trusted CA Indication"] (client side) of [RFC5246] (see
>           Section 3.1 (1) )
>=20
>        *  Implementations SHOULD allow to configure a list of=20
> acceptable
>           certificates, identified via certificate fingerprint.
>=20
[Joe] I would suggest specifying a format for interop here.  You might =
want to take a look at=20
http://tools.ietf.org/html/draft-ietf-syslog-transport-tls-14 which is =
somewhat similar and has some text on fingerprint matching. =20

>        *  Peer validation always includes a check on whether the DNS
>           name or the IP address of the server that is=20
> contacted matches
>           its certificate.  DNS names and IP addresses can be=20
> contained
>           in the Common Name (CN) or subjectAltName entries.  For
>           verification, only one these entries is to be=20
> considered.  The
>           following precedence applies: for DNS name validation,
>           subjectAltName:DNS has precedence over CN; for IP address
>           validation, subjectAltName:iPAddr has precedence over CN.
>=20
[Joe] In the syslog document referenced above we made it mandatory to =
support subjectAltName:DNSname matching.   Other places for the identity =
are allowed. =20

>        *  Implementations SHOULD allow to configure a set of=20
> acceptable
>           values for subjectAltName:URI.
>=20
[Joe] What does the URI look like? =20

> There's no additional text in Security Considerations since=20
> was not sure if additional text was needed with this new text.
>=20
> Please comment if this text can satisfactorily close this sub-issue.
>=20
> Greetings,
>=20
> Stefan Winter
>=20
> --
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education=20
> Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20
>=20

Delivery-date: Tue, 03 Mar 2009 15:23:56 +0000
Date: Tue, 3 Mar 2009 10:23:05 -0500
Subject: Issue 283: status-server
From: Greg Weber <[email-masked]>
To: "[email-masked]" <[email-masked]>
Cc: [email-masked]

The -04 revision of the status-server draft resolves all the comments I mad=
e on
the -02 revision (recorded as Issue 283), so I think that issue can be clos=
ed.

Regards, Greg

---------- Forwarded message ----------
From:  <[email-masked]>
Date: 2009/3/2
Subject: I-D ACTION:draft-ietf-radext-status-server-04.txt
To: [email-masked]
Cc: [email-masked]

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 IET=
F.

=A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Use of Status-Server Packets in =
the Remote
Authentication Dial In User Service (RADIUS) Protocol
=A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : A. DeKok
=A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-radext-status-server-04=
.txt
=A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 24
=A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2009-3-2

RFC 2865 defines a Status-Server code for use in RADIUS, but labels
=A0 it as "Experimental" without further discussion. =A0This document
=A0 describes a practical use for the Status-Server packet code, which is
=A0 to let clients query the status of a RADIUS server. =A0These queries,
=A0 and responses (if any) enable the client to make more informed
=A0 decisions. =A0The result is a more stable, and more robust RADIUS
=A0 architecture.

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

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

Delivery-date: Mon, 02 Mar 2009 22:06:08 +0000
From: Bernard Aboba <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: IETF 74 Agenda - Take One
Date: Mon, 2 Mar 2009 14:05:48 -0800

--_074183b1-4338-46ab-9e31-4a4d401e4d77_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

At IETF 74=2C the RADEXT WG is currently scheduled to meet on March 23=2C20=
09  from 9 AM - 11:30 AM.=20
Currently the Agenda is as follows:
=20
9 AM - 9:10 Preliminaries (10 minutes)
   Blue Sheets
   Note Takers
   Jabber Scribe
   Agenda bashing
   Document Status
=20
Documents completing IESG Evaluation (10 minutes)
=20
9:10 - 9:20 AM  RADIUS Authorization for NAS Management=2C David Nelson (5 =
minutes)
http://tools.ietf.org/html/draft-ietf-radext-management-authorization

Documents in Last Look (10 minutes)
=20
9:20 - 9:30 AM RADIUS Design Guidelines=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design
=20
Documents that have completed RADEXT WG Last Call (40 minutes)

=20

9:30 AM - 9:40 AM Status-Server=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server
=20
9:40 AM - 9:50 AM RADSEC=2C Stefan Winter (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec

=20

9:50 AM - 10:00 AM Extended RADIUS Attributes=2C TBD (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-extended-attributes

=20

10:00 AM - 10:10 AM RADIUS Cryptoagility Requirements=2C David Nelson (10 m=
inutes)
http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements
 =20
Working Group Work Items (30 minutes)
=20
10:10 AM - 10:20 AM TCP Transport=2C Alan DeKok (10 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:20 AM - 10:25 AM New Tunnel-Type Values=2C Abhishek Tiwari (5 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tunnel-type

Summary & Wrapup

--_074183b1-4338-46ab-9e31-4a4d401e4d77_
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'>
At IETF 74=2C the RADEXT WG is currently scheduled to meet on March 23=2C20=
09&nbsp=3B from 9 AM - 11:30 AM. <br>Currently the Agenda is as follows:<br=
>&nbsp=3B<br>9 AM - 9:10 Preliminaries (10 minutes)<br>&nbsp=3B&nbsp=3B Blu=
e Sheets<br>&nbsp=3B&nbsp=3B Note Takers<br>&nbsp=3B&nbsp=3B Jabber Scribe<=
br>&nbsp=3B&nbsp=3B Agenda bashing<br>&nbsp=3B&nbsp=3B Document Status<br>&=
nbsp=3B<br>Documents completing IESG Evaluation (10 minutes)<br>&nbsp=3B<br=
>9:10 - 9:20 AM&nbsp=3B RADIUS Authorization for NAS Management=2C David Ne=
lson (5 minutes)<br><font style=3D"" color=3D"#0066cc"><u>http://tools.ietf=
.org/html/draft-ietf-radext-management-authorization</u></font><br><br>Docu=
ments in Last Look (10 minutes)<br>&nbsp=3B<br>9:20 - 9:30 AM RADIUS Design=
 Guidelines=2C Alan DeKok (10 minutes)<br><a href=3D"http://tools.ietf.org/=
html/draft-ietf-radext-design-05" target=3D"_blank" rel=3D"nofollow"><u><fo=
nt color=3D"#0066cc">http://tools.ietf.org/html/draft-ietf-radext-design</f=
ont></u></a><br>&nbsp=3B<br>Documents that have completed RADEXT WG Last Ca=
ll (40 minutes)<br>
&nbsp=3B<br>
9:30 AM - 9:40 AM Status-Server=2C Alan DeKok (10 minutes)<br><a href=3D"ht=
tp://tools.ietf.org/html/draft-ietf-radext-status-server-02" target=3D"_bla=
nk" rel=3D"nofollow"><u><font color=3D"#800080">http://tools.ietf.org/html/=
draft-ietf-radext-status-server</font></u></a><br>&nbsp=3B<br>9:40 AM - 9:5=
0 AM RADSEC=2C Stefan Winter (10 minutes)<br><a href=3D"http://tools.ietf.o=
rg/html/draft-ietf-radext-radsec-02" target=3D"_blank" rel=3D"nofollow"><u>=
<font color=3D"#0066cc">http://tools.ietf.org/html/draft-ietf-radext-radsec=
</font></u></a><br>
&nbsp=3B<br>
9:50 AM -&nbsp=3B10:00 AM Extended RADIUS Attributes=2C TBD (10 minutes)<br=
><font style=3D"" color=3D"#444444"><a rel=3D"nofollow" href=3D"http://tool=
s.ietf.org/html/draft-ietf-radext-extended-attributes-05">http://tools.ietf=
.org/html/draft-ietf-radext-extended-attributes</a></font><br>
&nbsp=3B<br>
10:00&nbsp=3BAM - 10:10 AM RADIUS Cryptoagility Requirements=2C David Nelso=
n (10 minutes)<br><a href=3D"http://tools.ietf.org/html/draft-ietf-radext-c=
rypto-agility-requirements-02" target=3D"_blank" rel=3D"nofollow"><u><font =
color=3D"#0066cc">http://tools.ietf.org/html/draft-ietf-radext-crypto-agili=
ty-requirements</font></u></a><br>&nbsp=3B&nbsp=3B<br>Working Group Work It=
ems (30 minutes)<br>&nbsp=3B<br>10:10 AM - 10:20 AM TCP Transport=2C Alan D=
eKok (10 minutes)<br>http://tools.ietf.org/html/draft-ietf-radext-tcp-trans=
port<br><br>
10:20 AM - 10:25 AM New Tunnel-Type Values=2C Abhishek Tiwari (5 minutes)<b=
r><font style=3D"" color=3D"#0066cc"><u>http://tools.ietf.org/html/draft-ie=
tf-radext-tunnel-type</u></font><br><br>Summary &amp=3B Wrapup<br><table st=
yle=3D"border-top: 1px solid black=3B font-weight: bold=3B font-family: 'Se=
goe UI'=2CTahoma=2Csan-serif=3B"><tbody><tr><td><br></td></tr></tbody></tab=
le></body>
</html>=

--_074183b1-4338-46ab-9e31-4a4d401e4d77_--

Delivery-date: Mon, 02 Mar 2009 21:46:20 +0000
From: [email-masked]
To: [email-masked]
Cc: [email-masked]
Subject: I-D ACTION:draft-ietf-radext-status-server-04.txt 
Date: Mon,  2 Mar 2009 13:45:02 -0800 (PST)

--NextPart

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

	Title		: 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-04.txt
	Pages		: 24
	Date		: 2009-3-2
	
RFC 2865 defines a Status-Server code for use in RADIUS, but labels
   it as "Experimental" without further discussion.  This document
   describes a practical use for the Status-Server packet code, which is
   to let clients query the status of a RADIUS server.  These queries,
   and responses (if any) enable the client to make more informed
   decisions.  The result is a more stable, and more robust RADIUS
   architecture.

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

Content-Type: text/plain
Content-ID:	<[email-masked]>

--NextPart--

Delivery-date: Sun, 01 Mar 2009 15:01:30 +0000
From: [email-masked]
To: [email-masked]
Cc: [email-masked]
Subject: I-D Action:draft-ietf-radext-tcp-transport-03.txt 
Date: Sun,  1 Mar 2009 07:00:01 -0800 (PST)

--NextPart

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

	Title           : RADIUS Over TCP
	Author(s)       : A. DeKok
	Filename        : draft-ietf-radext-tcp-transport-03.txt
	Pages           : 17
	Date            : 2009-03-01

The Remote Authentication Dial In User Server (RADIUS) Protocol has
traditionally used the User Datagram Protocol (UDP) as it's
underlying transport layer.  This document defines RADIUS over the
Transmission Control Protocol (TCP).

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

Content-Type: text/plain
Content-ID:     <[email-masked]>

--NextPart--