IETF-67 RADEXT Agenda Take One

["Nelson, David" <dnelson@enterasys.com>]

Proposed Agenda for RADEXT at IETF-67.

Please comment.  BTW, it would be very helpful for attendees to have
read the relevant drafts.  Draft authors who are available to present,
please respond to the chairs, so that we can fill in the TBDs.

-----------------------------------------------------------------------
Agenda for the RADEXT WG Meeting at IETF 67
Tuesday, November 7, 2006, Morning Session I 0900-1130
Room Name: Harbor Island I

WGs meeting at the same time: widex, 16ng, trill, avt, dkim, ippm,
rserpool  

A. Preliminaries, Note Takers, Jabber Scribes, Blue Sheets (5 minutes)

B. Agenda Bashing

C. Milestone Status Review (5 minutes)

C.1  Discussion of RADEXT Crypto-Agility work item descriptive text.
(10 minutes)

D. Document Status

D.1  Documents with errata

D.1.1  RFC 4590 has an error in the IANA assignment for a RADIUS
Attribute Type ID.  Discuss whether this can be handled by an RFC Editor
Errata note, or whether it requires an RFC4590bis ID to correct the
error.
http://www.ietf.org/rfc/rfc4590.txt.  (TBD, 5 minutes)
 
D.2  Documents in IESG review

D.2.1  draft-ietf-radext-delegated-prefix-05.txt.  (TBD, 5 minutes)

D.3  Documents in Pre-WG review

D.3.1  NAS-Filter-Rule Attributes (Mauricio Sanchez, 10 minutes)
http://www.ietf.org/internet-drafts/draft-ietf-radext-filter-04.txt 

D.3.2  NAS-Traffic-Rule Attributes (Mauricio Sanchez, 15 minutes)
http://www.ietf.org/internet-drafts/draft-ietf-radext-filter-rules-01.tx
t 

D.3.3  Extended RADIUS Attributes (TBD, 20 minutes)
http://www.ietf.org/draft-lior-radius-attribute-type-extension-01.txt

General Discussion of Extended Attributes, using this draft as a
straw-man proposal. (WG at large, 30 minutes)
 
D.3.4  Issues & Fixes (TBD, 10 minutes)
http://www.ietf.org/internet-drafts/draft-aboba-radext-fixes-03.txt

D.4  Documents requiring cross-WG review

D.4.1  RADIUS Mobile IPv6 Support (TBD, 10 minutes)
http://www.ietf.org/internet-drafts/draft-ietf-mip6-radius-01.txt

E. Next Steps

E.1  Is it sufficient for the RADIUS Prepaid Attributes work to be
published as an Informational RFC, using Vendor Specific Attributes? (10
minutes)

E.2  The RADIUS WLAN Attributes work is waiting on a finalization of
requirements form IEEE 802.11r.  What should we do with this work item?
(5 minutes)

E.3  Do we need a BCP on attribute design for "classic attributes" or do
we only need a design guideline for "extended attributes"? (10 minutes)


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