60 likes | 179 Vues
This document outlines the RADEXT Dynamic Authentication Management Information Bases (MIBs), presented at IETF-64 in Vancouver. It includes details on the drafts currently under WG Last Call, the status of various issues raised, and instructions for submitting comments. Key topics include the handling of session counters, editorial issues, and IANA registrations. The information is crucial for those involved in the development and implementation of RADIUS extensions, and feedback is welcomed from the community.
E N D
RADEXT Dynauth MIBs Stefaan De Cnodder Nagi Jonnala Murtaza Chiba (presented by Greg Weber) IETF-64, Vancouver
J F M A M J J A S O N D 2004 J F M A M J J A S O N D 2005 RADEXT Dynauth MIBs draft-ietf-radext-dynauth-client-mib-02.txt draft-ietf-radext-dynauth-server-mib-02.txt • Companions to RFC 3576 • WG work item • Informational track • One WG LC complete • Charter Milestone:to IESG Dec ’05 WG-00 Indiv-03 Indiv-01 WG-01 Indiv-02 Indiv-00 WG-02 DraftRevisions Milestones Accepted as WG item WG LC1 begin Completion target WG LC1 end WG LC2 begin IETF-64, Vancouver
RADEXT Dynauth MIBs Currently in WG Last Call • WG Last call until:Monday, November 14th • Please send comments to the list- radiusext@ops.ietf.org • Use the issue format here:http://www.drizzle.com/~aboba/RADEXT/ • Last Call announcement:http://ops.ietf.org/lists/radiusext/2005/msg00987.html IETF-64, Vancouver
RADEXT Dynauth MIBs Issues New issue • Issue 137 (t): Session Counters (discuss) Resolved or addressed in -02 • Issue 92 (e): Editorial & DAC/DAS terms (accept) • Issue 96/97 (e): Editorial comments (discuss) • Issue 105 (t): IANA registration (discuss) IETF-64, Vancouver
RADEXT Dynauth MIBs Issue 137 – Pending Do we need counters for ‘session context not found’ and other errors? • Are there security issues with revealing too much information? • What are the Diameter RAR interactions? IETF-64, Vancouver
RADEXT Dynauth MIBs • Questions? • If you have reviewed, please respond even if you have no new issues to file. IETF-64, Vancouver