130 likes | 155 Views
This document outlines the status and major changes in the Diameter-NASREQ-10 specification from IETF 55 - AAA WG. Major updates include reorganized sections, removal of EAP, and added AVPs for better interaction with RADIUS. The issues list, closed items, and ongoing points are detailed, leading to the final publication. Relevant links and resources are provided for further reference and collaboration.
E N D
Diameter-Nasreq-10 Dave Mitton, Most recent Document Editor With Contributions from David Spence & Glen Zorn IETF 55 - AAA WG, NASREQ-10
Status of Document • Missed publication deadline http://home.attbi.com/~dmitton/draft-ietf-aaa-diameter-nasreq-10.txt • Will be published when Editor reopens • Document going to Last Call IETF 55 - AAA WG, NASREQ-10
Major Changes since -09 • Sections reorganized to flow top down: • Session operations, Message Commands, • AVPs: • Session • Authentication • Authorization, Common • Service Specific Authorization • Tunneling • Accounting • RADIUS interactions IETF 55 - AAA WG, NASREQ-10
Major Changes, continued • EAP Removed – See draft-ietf-aaa-eap-00.txt • Added mapping of RADIUS Acct-Termination-Cause to Termination-Cause AVP • RADIUS Interaction Section upgraded • VSA Handling added IETF 55 - AAA WG, NASREQ-10
Vendor AVP mapping IETF 55 - AAA WG, NASREQ-10
Issues List Locations • Diameter WG Issues list: • http://www.drizzle.com/~aboba/AAA/issues.html • Dave Spence’s NASReq Editors list: • http://ext.interlinknetworks.com/dspence/nasreq.html IETF 55 - AAA WG, NASREQ-10
Issues Closed • 255 – RADIUS VSA translation • 295 – RADIUS AVPs needed • 297 – Nasreq values for Termination-Cause (Zorn, Hiller) • 308 – Originating-Line-Info AVP added • 321 – Normative references to CMS • 347 – RADIUS/Diameter Interactions • 348 – Nasreq references normative/non • 355 – Remove Keying AVPs IETF 55 - AAA WG, NASREQ-10
Dave Spence’s Editor’s List • Remove EAP and key distribution stuff - Done • Write a proper accounting section – Sort of • Occurrence tables for ACRs and ACAs are inaccurate and incomplete - Done • Reconcile AVP descriptions with corresponding RADIUS descriptions - Open • Find out whether IEEE 802.1x Annex D (IEEE 802.1x RADIUS Usage Guidelines) should be incorporated into Diameter-NASREQ – No. • Consider reorganization of sections and subsections -Done • Check that all AVPs appear in all the correct places - Done • Proofread – Need more eyes IETF 55 - AAA WG, NASREQ-10
Issues Still Open • Typographical & Table Formatting fixups • Accounting description good enough? • Pull up more RADIUS referral text? • Do the RADIUS interaction rules for Origin-Host, and Origin-Realm AVPs work as needed? • Should clarify User-Password & Tunnel-Password data • 331 – ABNF not in RFC 2234 format • 379 – Nits on pre-submission version • 380 – Various questions • 381 – Additional Accounting AVPs requested IETF 55 - AAA WG, NASREQ-10
Issue 331 – Preview NitsSubmitter: Bernard Aboba IETF 55 - AAA WG, NASREQ-10
Issue 380 – Various issuesSubmitter name: Sukjoon Lee • Transaction state observation • Multi-Round Timeout in latest Base • Route-Record AVP? • Session-Key gone to EAP doc • Acct-Session-Id <= Acct-RADIUS-Session-Id AVP (rename back) IETF 55 - AAA WG, NASREQ-10
Issue 381- Authorization Limits AVPsSubmitter name: Valery Kholodkov • Input-Octets-LimitThis attribute specifies maximum number of octets to be received from user before termination of session or prompt. If this attribute is not specified and Input-Gigawords-Limit attribute is not specified the maximum number of octets to be received from user is unlimited. • Output-Octets-LimitThis attribute specifies maximum number of octets to be sent to user before termination of session or prompt. If this attribute is not specified and Output-Gigawords-Limit attribute is not specified the maximum number of octets to be sent to user is unlimited. • Input-Gigawords-LimitThis attribute specifies maximum number of gigawords to be received from user before termination of session or prompt. If this attribute is not specified the maximum number of octets to be received from user is defined by Input-Octets-Limit attribute. • Output-Gigawords-LimitThis attribute specifies maximum number of gigawords to be sent to user before termination of session or prompt. If this attribute is not specified the maximum number of octets to be sent to user is defined by Output-Octets-Limit attribute. • Input-Packets-LimitThis attribute specifies maximum number of packets to be received from user before termination of session or prompt. • Output-Packets-LimitThis attribute specifies maximum number of packets to be sent to user before termination of session or prompt. IETF 55 - AAA WG, NASREQ-10