1. 11/20/2002IETF 55 - AAA WG, NASREQ-101 Diameter-Nasreq-10 Dave Mitton, Most recent Document Editor With Contributions from David Spence & Glen Zorn

2. 11/20/2002IETF 55 - AAA WG, NASREQ-102 Status of Document Missed publication deadline http://home.attbi.com/~dmitton/draft-ietf- aaa-diameter-nasreq-10.txt http://home.attbi.com/~dmitton/draft-ietf- aaa-diameter-nasreq-10.txt Will be published when Editor reopens Document going to Last Call

3. 11/20/2002IETF 55 - AAA WG, NASREQ-103 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

4. 11/20/2002IETF 55 - AAA WG, NASREQ-104 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

5. 11/20/2002IETF 55 - AAA WG, NASREQ-105 Vendor AVP mapping

6. 11/20/2002IETF 55 - AAA WG, NASREQ-106 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

7. 11/20/2002IETF 55 - AAA WG, NASREQ-107 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

8. 11/20/2002IETF 55 - AAA WG, NASREQ-108 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

9. 11/20/2002IETF 55 - AAA WG, NASREQ-109 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

10. 11/20/2002IETF 55 - AAA WG, NASREQ-1010 Issue 331 – Preview Nits Submitter: Bernard Aboba

11. 11/20/2002IETF 55 - AAA WG, NASREQ-1011 Issue 380 – Various issues Submitter 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)

12. 11/20/2002IETF 55 - AAA WG, NASREQ-1012 Issue 381- Authorization Limits AVPs Submitter name: Valery Kholodkov Input-Octets-Limit This 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-Limit This 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-Limit This 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-Limit This 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-Limit This attribute specifies maximum number of packets to be received from user before termination of session or prompt. Output-Packets-Limit This attribute specifies maximum number of packets to be sent to user before termination of session or prompt.

13. 11/20/2002IETF 55 - AAA WG, NASREQ-1013