1. Aug 3, 2004AAA WG, IETF 60 San Diego1 Diameter NASReq Application Status David Mitton, Document Editor

2. Aug 3, 2004AAA WG, IETF 60 San Diego2 Current Document draft-ietf-aaa-nasreq-17.txt http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-nasreq-17.txt http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-nasreq-17.txt –Published July 27, 2004 –Draft 16 incorporated IESG review comments –Draft 17 some last minute found bugs –This document is going to the RFC Editor

3. Aug 3, 2004AAA WG, IETF 60 San Diego3 Changes in Draft 15 Edits: –Fix Acct-Session-ID in ABNFs –Re-add missing code points for NAS-Port-Type –Tunnel-Client-Auth-ID, Tunnel-Server-Auth-ID defined as UTF8Strings (Were Unsigned32 in table, OctetString in description) - Tunnel-Private-Group-ID OctetString Issues: 431 - Identities in RADIUS Translation, 1&2) State attribute should contain Diameter/ / / 3) State content building should be consistent 4) Fix section 9.3 for Origin-Host to identify NAS source, not gateway 5) Corrected. Though it may introduce an ambiguity in routing. 6) Origin-Realm from NAS FQDN and admin table Changed text in sect 9 wrt to session retention Improve mapping of target identities RADIUS/Diameter A Session-Id AVP must be created by the agent Origin-Host AVP should contain best verified info on NAS identity (not the gateway) 451 - Interim vs. STOP Record, a) Compromise - add text to allow Stop/Start as service specific b) Editorial correction Accepted 453 - Problem with Accounting Session-Id and Session-Id - Acct-Session-Id cannot be put in Diam Session-Id. Acct-Session-Id is an accepted Diameter AVP. A RADIUS/Diameter gateway will have to assign & track Diameter Session-Ids. 454 - Diameter NASREQ conflict with Base, Closed: Text already changed in draft 14 457 - Editorial NIT in NASREQ-14 - Updated Service-Type list Section 6.10 restricts use of IP service AVPs to a specific list of Framed-Protocol values, which has changed. Accepted: the list has been removed. Similar list removed from IPX and ARAP sections

4. Aug 3, 2004AAA WG, IETF 60 San Diego4 Changes in Draft 16 Input from List, AD, prior IESG review comments, IETF Process changes Changed Abstract, IPR and copyright statements to conform to process of RFC3667 Added text to Abstract and Overview that the description of RADIUS interactions apply to all Diameter applications. Added referral to UTF-8 reference Other Editorial corrections

5. Aug 3, 2004AAA WG, IETF 60 San Diego5 Changes in Draft 17 Issues 464: Clarify use of NAS Application-ID in CER, AAR 466: Missing "[Failed AVP]" in AAA ABNF A number of ABNF error AVP inconsistencies were corrected 468: Added QoS-Filter-Rule AVP (407) –Completed data type description in Base –Text recovered from old Base copies –AVP required by NASreq Criteria (RFC ) Readjusted tables and page breaks

6. Aug 3, 2004AAA WG, IETF 60 San Diego6 Next Steps Requested for RFC publication Declare victory Consider RADIUS/Diameter Interactions document