< draft-ietf-aaa-diameter-nasreq-16.txt   draft-ietf-aaa-diameter-nasreq-17.txt >
AAA Working Group Pat R. Calhoun AAA Working Group Pat R. Calhoun
Internet-Draft Airespace Inc. Internet-Draft Airespace Inc.
Category: Standards Track Glen Zorn Category: Standards Track Glen Zorn
Cisco Systems Inc. Cisco Systems Inc.
David Spence David Spence
David Mitton David Mitton
Circular Networks Circular Networks
Jun 2004 Jul 2004
Diameter Network Access Server Application Diameter Network Access Server Application
draft-ietf-aaa-diameter-nasreq-16.txt draft-ietf-aaa-diameter-nasreq-17.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 3 of RFC3667. all provisions of Section 3 of RFC3667.
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with and any of which I become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 3, line 17 skipping to change at page 3, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . 7 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . 7
1.2. Requirements Language . . . . . . . . . . . . . . . . . 8 1.2. Requirements Language . . . . . . . . . . . . . . . . . 8
1.3. Advertising Application Support . . . . . . . . . . . . 8 1.3. Advertising Application Support . . . . . . . . . . . . 8
2. NAS Calls, Ports, and Sessions . . . . . . . . . . . . . . . . . 8 2. NAS Calls, Ports, and Sessions . . . . . . . . . . . . . . . . . 8
2.1. Diameter Session Establishment . . . . . . . . . . . . . 9 2.1. Diameter Session Establishment . . . . . . . . . . . . . 9
2.2. Diameter Session Reauthentication or Reauthorization . . 9 2.2. Diameter Session Reauthentication or Reauthorization . . 9
2.3. Diameter Session Termination . . . . . . . . . . . . . . 10 2.3. Diameter Session Termination . . . . . . . . . . . . . . 10
3. NAS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3. NAS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1. AA-Request (AAR) Command . . . . . . . . . . . . . . . . 11 3.1. AA-Request (AAR) Command . . . . . . . . . . . . . . . . 11
3.2. AA-Answer (AAA) Command . . . . . . . . . . . . . . . . 14 3.2. AA-Answer (AAA) Command . . . . . . . . . . . . . . . . 13
3.3. Re-Auth-Request (RAR) Command . . . . . . . . . . . . . 16 3.3. Re-Auth-Request (RAR) Command . . . . . . . . . . . . . 15
3.4. Re-Auth-Answer (RAA) Command . . . . . . . . . . . . . . 17 3.4. Re-Auth-Answer (RAA) Command . . . . . . . . . . . . . . 16
3.5. Session-Termination-Request (STR) Command . . . . . . . 18 3.5. Session-Termination-Request (STR) Command . . . . . . . 17
3.6. Session-Termination-Answer (STA) Command . . . . . . . . 19 3.6. Session-Termination-Answer (STA) Command . . . . . . . . 18
3.7. Abort-Session-Request (ASR) Command . . . . . . . . . . 19 3.7. Abort-Session-Request (ASR) Command . . . . . . . . . . 18
3.8. Abort-Session-Answer (ASA) Command . . . . . . . . . . . 20 3.8. Abort-Session-Answer (ASA) Command . . . . . . . . . . . 19
3.9. Accounting-Request (ACR) Command . . . . . . . . . . . . 21 3.9. Accounting-Request (ACR) Command . . . . . . . . . . . . 20
3.10. Accounting-Answer (ACA) Command . . . . . . . . . . . . 23 3.10. Accounting-Answer (ACA) Command . . . . . . . . . . . . 22
4. NAS Session AVPs . . . . . . . . . . . . . . . . . . . . . . . . 24 4. NAS Session AVPs . . . . . . . . . . . . . . . . . . . . . . . . 23
4.1. Call and Session Information . . . . . . . . . . . . . . 25 4.1. Call and Session Information . . . . . . . . . . . . . . 24
4.2. NAS-Port AVP . . . . . . . . . . . . . . . . . . . . . . 25 4.2. NAS-Port AVP . . . . . . . . . . . . . . . . . . . . . . 24
4.3. NAS-Port-Id AVP . . . . . . . . . . . . . . . . . . . . 26 4.3. NAS-Port-Id AVP . . . . . . . . . . . . . . . . . . . . 25
4.4. NAS-Port-Type AVP . . . . . . . . . . . . . . . . . . . 26 4.4. NAS-Port-Type AVP . . . . . . . . . . . . . . . . . . . 25
4.5. Called-Station-Id AVP . . . . . . . . . . . . . . . . . 27 4.5. Called-Station-Id AVP . . . . . . . . . . . . . . . . . 26
4.6. Calling-Station-Id AVP . . . . . . . . . . . . . . . . . 27 4.6. Calling-Station-Id AVP . . . . . . . . . . . . . . . . . 26
4.7. Connect-Info AVP . . . . . . . . . . . . . . . . . . . . 28 4.7. Connect-Info AVP . . . . . . . . . . . . . . . . . . . . 27
4.8. Originating-Line-Info AVP . . . . . . . . . . . . . . . 28 4.8. Originating-Line-Info AVP . . . . . . . . . . . . . . . 27
4.9. Reply-Message AVP . . . . . . . . . . . . . . . . . . . 29 4.9. Reply-Message AVP . . . . . . . . . . . . . . . . . . . 28
5. NAS Authentication AVPs . . . . . . . . . . . . . . . . . . . . 30 5. NAS Authentication AVPs . . . . . . . . . . . . . . . . . . . . 29
5.1. User-Password AVP . . . . . . . . . . . . . . . . . . . 30 5.1. User-Password AVP . . . . . . . . . . . . . . . . . . . 30
5.2. Password-Retry AVP . . . . . . . . . . . . . . . . . . . 31 5.2. Password-Retry AVP . . . . . . . . . . . . . . . . . . . 30
5.3. Prompt AVP . . . . . . . . . . . . . . . . . . . . . . . 31 5.3. Prompt AVP . . . . . . . . . . . . . . . . . . . . . . . 30
5.4. CHAP-Auth AVP . . . . . . . . . . . . . . . . . . . . . 31 5.4. CHAP-Auth AVP . . . . . . . . . . . . . . . . . . . . . 30
5.5. CHAP-Algorithm AVP . . . . . . . . . . . . . . . . . . . 32 5.5. CHAP-Algorithm AVP . . . . . . . . . . . . . . . . . . . 31
5.6. CHAP-Ident AVP . . . . . . . . . . . . . . . . . . . . . 32 5.6. CHAP-Ident AVP . . . . . . . . . . . . . . . . . . . . . 31
5.7. CHAP-Response AVP . . . . . . . . . . . . . . . . . . . 32 5.7. CHAP-Response AVP . . . . . . . . . . . . . . . . . . . 31
5.8. CHAP-Challenge AVP . . . . . . . . . . . . . . . . . . . 32 5.8. CHAP-Challenge AVP . . . . . . . . . . . . . . . . . . . 31
5.9. ARAP-Password AVP . . . . . . . . . . . . . . . . . . . 32 5.9. ARAP-Password AVP . . . . . . . . . . . . . . . . . . . 31
5.10. ARAP-Challenge-Response AVP . . . . . . . . . . . . . . 33 5.10. ARAP-Challenge-Response AVP . . . . . . . . . . . . . . 32
5.11. ARAP-Security AVP . . . . . . . . . . . . . . . . . . . 33 5.11. ARAP-Security AVP . . . . . . . . . . . . . . . . . . . 32
5.12. ARAP-Security-Data AVP . . . . . . . . . . . . . . . . 33 5.12. ARAP-Security-Data AVP . . . . . . . . . . . . . . . . 32
6. NAS Authorization AVPs . . . . . . . . . . . . . . . . . . . . . 33 6. NAS Authorization AVPs . . . . . . . . . . . . . . . . . . . . . 32
6.1. Service-Type AVP . . . . . . . . . . . . . . . . . . . . 35 6.1. Service-Type AVP . . . . . . . . . . . . . . . . . . . . 34
6.2. Callback-Number AVP . . . . . . . . . . . . . . . . . . 36 6.2. Callback-Number AVP . . . . . . . . . . . . . . . . . . 35
6.3. Callback-Id AVP . . . . . . . . . . . . . . . . . . . . 36 6.3. Callback-Id AVP . . . . . . . . . . . . . . . . . . . . 35
6.4. Idle-Timeout AVP . . . . . . . . . . . . . . . . . . . . 36 6.4. Idle-Timeout AVP . . . . . . . . . . . . . . . . . . . . 35
6.5. Port-Limit AVP . . . . . . . . . . . . . . . . . . . . . 37 6.5. Port-Limit AVP . . . . . . . . . . . . . . . . . . . . . 36
6.6. NAS-Filter-Rule AVP . . . . . . . . . . . . . . . . . . 37 6.6. NAS-Filter-Rule AVP . . . . . . . . . . . . . . . . . . 36
6.7. Filter-Id AVP . . . . . . . . . . . . . . . . . . . . . 37 6.7. Filter-Id AVP . . . . . . . . . . . . . . . . . . . . . 36
6.8. Configuration-Token AVP . . . . . . . . . . . . . . . . 37 6.8. Configuration-Token AVP . . . . . . . . . . . . . . . . 36
6.9. Framed Access Authorization AVPs . . . . . . . . . . . . 38 6.9. QoS-Filter-Rule AVP . . . . . . . . . . . . . . . . . . 37
6.9.1. Framed-Protocol AVP . . . . . . . . . . . . . 38 6.10. Framed Access Authorization AVPs . . . . . . . . . . . 38
6.9.2. Framed-Routing AVP . . . . . . . . . . . . . . 38 6.10.1. Framed-Protocol AVP . . . . . . . . . . . . . 38
6.9.3. Framed-MTU AVP . . . . . . . . . . . . . . . . 38 6.10.2. Framed-Routing AVP . . . . . . . . . . . . . 39
6.9.4. Framed-Compression AVP . . . . . . . . . . . . 39 6.10.3. Framed-MTU AVP . . . . . . . . . . . . . . . 39
6.10. IP Access Authorization AVPs . . . . . . . . . . . . . 39 6.10.4. Framed-Compression AVP . . . . . . . . . . . 39
6.10.1. Framed-IP-Address AVP . . . . . . . . . . . . 39 6.11. IP Access Authorization AVPs . . . . . . . . . . . . . 40
6.10.2. Framed-IP-Netmask AVP . . . . . . . . . . . . 39 6.11.1. Framed-IP-Address AVP . . . . . . . . . . . . 40
6.10.3. Framed-Route AVP . . . . . . . . . . . . . . 40 6.11.2. Framed-IP-Netmask AVP . . . . . . . . . . . . 40
6.10.4. Framed-Pool AVP . . . . . . . . . . . . . . . 40 6.11.3. Framed-Route AVP . . . . . . . . . . . . . . 40
6.10.5. Framed-Interface-Id AVP . . . . . . . . . . . 40 6.11.4. Framed-Pool AVP . . . . . . . . . . . . . . . 41
6.10.6. Framed-IPv6-Prefix AVP . . . . . . . . . . . 41 6.11.5. Framed-Interface-Id AVP . . . . . . . . . . . 41
6.10.7. Framed-IPv6-Route AVP . . . . . . . . . . . . 41 6.11.6. Framed-IPv6-Prefix AVP . . . . . . . . . . . 41
6.10.8. Framed-IPv6-Pool AVP . . . . . . . . . . . . 41 6.11.7. Framed-IPv6-Route AVP . . . . . . . . . . . . 41
6.11. IPX Access . . . . . . . . . . . . . . . . . . . . . . 41 6.11.8. Framed-IPv6-Pool AVP . . . . . . . . . . . . 42
6.11.1. Framed-IPX-Network AVP . . . . . . . . . . . 42 6.12. IPX Access . . . . . . . . . . . . . . . . . . . . . . 42
6.12. AppleTalk Network Access . . . . . . . . . . . . . . . 42 6.12.1. Framed-IPX-Network AVP . . . . . . . . . . . 42
6.12.1. Framed-AppleTalk-Link AVP . . . . . . . . . . 42 6.13. AppleTalk Network Access . . . . . . . . . . . . . . . 43
6.12.2. Framed-AppleTalk-Network AVP . . . . . . . . 42 6.13.1. Framed-AppleTalk-Link AVP . . . . . . . . . . 43
6.12.3. Framed-AppleTalk-Zone AVP . . . . . . . . . . 43 6.13.2. Framed-AppleTalk-Network AVP . . . . . . . . 43
6.13. AppleTalk Remote Access . . . . . . . . . . . . . . . . 43 6.13.3. Framed-AppleTalk-Zone AVP . . . . . . . . . . 43
6.13.1. ARAP-Features AVP . . . . . . . . . . . . . . 43 6.14. AppleTalk Remote Access . . . . . . . . . . . . . . . . 44
6.13.2. ARAP-Zone-Access AVP . . . . . . . . . . . . 43 6.14.1. ARAP-Features AVP . . . . . . . . . . . . . . 44
6.14. Non-Framed Access Authorization AVPs . . . . . . . . . 43 6.14.2. ARAP-Zone-Access AVP . . . . . . . . . . . . 44
6.14.1. Login-IP-Host AVP . . . . . . . . . . . . . . 44 6.15. Non-Framed Access Authorization AVPs . . . . . . . . . 44
6.14.2. Login-IPv6-Host AVP . . . . . . . . . . . . . 44 6.15.1. Login-IP-Host AVP . . . . . . . . . . . . . . 44
6.14.3. Login-Service AVP . . . . . . . . . . . . . . 44 6.15.2. Login-IPv6-Host AVP . . . . . . . . . . . . . 45
6.15. TCP Services . . . . . . . . . . . . . . . . . . . . . 45 6.15.3. Login-Service AVP . . . . . . . . . . . . . . 45
6.15.1. Login-TCP-Port AVP . . . . . . . . . . . . . 45 6.16. TCP Services . . . . . . . . . . . . . . . . . . . . . 45
6.16. LAT Services . . . . . . . . . . . . . . . . . . . . . 45 6.16.1. Login-TCP-Port AVP . . . . . . . . . . . . . 45
6.16.1. Login-LAT-Service AVP . . . . . . . . . . . . 45 6.17. LAT Services . . . . . . . . . . . . . . . . . . . . . 46
6.16.2. Login-LAT-Node AVP . . . . . . . . . . . . . 46 6.17.1. Login-LAT-Service AVP . . . . . . . . . . . . 46
6.16.3. Login-LAT-Group AVP . . . . . . . . . . . . . 46 6.17.2. Login-LAT-Node AVP . . . . . . . . . . . . . 46
6.16.4. Login-LAT-Port AVP . . . . . . . . . . . . . 47 6.17.3. Login-LAT-Group AVP . . . . . . . . . . . . . 47
7. NAS Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . 47 6.17.4. Login-LAT-Port AVP . . . . . . . . . . . . . 47
7. NAS Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.1. Tunneling AVP . . . . . . . . . . . . . . . . . . . . . 48 7.1. Tunneling AVP . . . . . . . . . . . . . . . . . . . . . 48
7.2. Tunnel-Type AVP . . . . . . . . . . . . . . . . . . . . 49 7.2. Tunnel-Type AVP . . . . . . . . . . . . . . . . . . . . 49
7.3. Tunnel-Medium-Type AVP . . . . . . . . . . . . . . . . . 49 7.3. Tunnel-Medium-Type AVP . . . . . . . . . . . . . . . . . 50
7.4. Tunnel-Client-Endpoint AVP . . . . . . . . . . . . . . . 50 7.4. Tunnel-Client-Endpoint AVP . . . . . . . . . . . . . . . 50
7.5. Tunnel-Server-Endpoint AVP . . . . . . . . . . . . . . . 51 7.5. Tunnel-Server-Endpoint AVP . . . . . . . . . . . . . . . 51
7.6. Tunnel-Password AVP . . . . . . . . . . . . . . . . . . 51 7.6. Tunnel-Password AVP . . . . . . . . . . . . . . . . . . 52
7.7. Tunnel-Private-Group-Id AVP . . . . . . . . . . . . . . 51 7.7. Tunnel-Private-Group-Id AVP . . . . . . . . . . . . . . 52
7.8. Tunnel-Assignment-Id AVP . . . . . . . . . . . . . . . . 52 7.8. Tunnel-Assignment-Id AVP . . . . . . . . . . . . . . . . 52
7.9. Tunnel-Preference AVP . . . . . . . . . . . . . . . . . 53 7.9. Tunnel-Preference AVP . . . . . . . . . . . . . . . . . 53
7.10. Tunnel-Client-Auth-Id AVP . . . . . . . . . . . . . . . 54 7.10. Tunnel-Client-Auth-Id AVP . . . . . . . . . . . . . . . 54
7.11. Tunnel-Server-Auth-Id AVP . . . . . . . . . . . . . . . 54 7.11. Tunnel-Server-Auth-Id AVP . . . . . . . . . . . . . . . 54
8. NAS Accounting . . . . . . . . . . . . . . . . . . . . . . . . . 54 8. NAS Accounting . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.1. Accounting-Input-Octets AVP . . . . . . . . . . . . . . 55 8.1. Accounting-Input-Octets AVP . . . . . . . . . . . . . . 56
8.2. Accounting-Output-Octets AVP . . . . . . . . . . . . . . 56 8.2. Accounting-Output-Octets AVP . . . . . . . . . . . . . . 56
8.3. Accounting-Input-Packets AVP . . . . . . . . . . . . . . 56 8.3. Accounting-Input-Packets AVP . . . . . . . . . . . . . . 57
8.4. Accounting-Output-Packets AVP . . . . . . . . . . . . . 56 8.4. Accounting-Output-Packets AVP . . . . . . . . . . . . . 57
8.5. Acct-Session-Time AVP . . . . . . . . . . . . . . . . . 56 8.5. Acct-Session-Time AVP . . . . . . . . . . . . . . . . . 57
8.6. Acct-Authentic AVP . . . . . . . . . . . . . . . . . . . 56 8.6. Acct-Authentic AVP . . . . . . . . . . . . . . . . . . . 57
8.7. Accounting-Auth-Method AVP . . . . . . . . . . . . . . . 57 8.7. Accounting-Auth-Method AVP . . . . . . . . . . . . . . . 57
8.8. Acct-Delay-Time . . . . . . . . . . . . . . . . . . . . 57 8.8. Acct-Delay-Time . . . . . . . . . . . . . . . . . . . . 58
8.9. Acct-Link-Count . . . . . . . . . . . . . . . . . . . . 57 8.9. Acct-Link-Count . . . . . . . . . . . . . . . . . . . . 58
8.10. Acct-Tunnel-Connection AVP . . . . . . . . . . . . . . 58 8.10. Acct-Tunnel-Connection AVP . . . . . . . . . . . . . . 59
8.11. Acct-Tunnel-Packets-Lost AVP . . . . . . . . . . . . . 59 8.11. Acct-Tunnel-Packets-Lost AVP . . . . . . . . . . . . . 59
9. RADIUS/Diameter Protocol Interactions . . . . . . . . . . . . . 59 9. RADIUS/Diameter Protocol Interactions . . . . . . . . . . . . . 59
9.1. RADIUS Request Forwarded as Diameter Request . . . . . . 59 9.1. RADIUS Request Forwarded as Diameter Request . . . . . . 60
9.1.1. RADIUS Dynamic Authorization considerations . 62 9.1.1. RADIUS Dynamic Authorization considerations . 63
9.2. Diameter Request Forwarded as RADIUS Request . . . . . . 63 9.2. Diameter Request Forwarded as RADIUS Request . . . . . . 64
9.2.1. RADIUS Dynamic Authorization considerations . 65 9.2.1. RADIUS Dynamic Authorization considerations . 65
9.3. AVPs Used Only for Compatibility . . . . . . . . . . . . 66 9.3. AVPs Used Only for Compatibility . . . . . . . . . . . . 67
9.3.1. NAS-Identifier AVP . . . . . . . . . . . . . . 67 9.3.1. NAS-Identifier AVP . . . . . . . . . . . . . . 67
9.3.2. NAS-IP-Address AVP . . . . . . . . . . . . . . 67 9.3.2. NAS-IP-Address AVP . . . . . . . . . . . . . . 68
9.3.3. NAS-IPv6-Address AVP . . . . . . . . . . . . . 68 9.3.3. NAS-IPv6-Address AVP . . . . . . . . . . . . . 69
9.3.4. State AVP . . . . . . . . . . . . . . . . . . 69 9.3.4. State AVP . . . . . . . . . . . . . . . . . . 69
9.3.5. Termination-Cause AVP Code Values . . . . . . 69 9.3.5. Termination-Cause AVP Code Values . . . . . . 70
9.4. Prohibited RADIUS Attributes . . . . . . . . . . . . . . 71 9.4. Prohibited RADIUS Attributes . . . . . . . . . . . . . . 72
9.5. Translatable Diameter AVPs . . . . . . . . . . . . . . . 72 9.5. Translatable Diameter AVPs . . . . . . . . . . . . . . . 73
9.6. RADIUS Vendor Specific Attributes . . . . . . . . . . . 72 9.6. RADIUS Vendor Specific Attributes . . . . . . . . . . . 73
9.6.1. Forwarding a Diameter Vendor AVP as a RADIUS VS 72 9.6.1. Forwarding a Diameter Vendor AVP as a RADIUS VS 73
9.6.2. Forwarding a RADIUS VSA to a Diameter Vendor AV 73 9.6.2. Forwarding a RADIUS VSA to a Diameter Vendor AV 74
10. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . . 74 10. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . . 75
10.1. AA-Request/Answer AVP Table . . . . . . . . . . . . . . 74 10.1. AA-Request/Answer AVP Table . . . . . . . . . . . . . . 75
10.2. Accounting AVP Tables . . . . . . . . . . . . . . . . . 77 10.2. Accounting AVP Tables . . . . . . . . . . . . . . . . . 78
10.2.1. Accounting Framed Access AVP Table . . . . . 77 10.2.1. Accounting Framed Access AVP Table . . . . . 78
10.2.2. Accounting Non-Framed Access AVP Table . . . 79 10.2.2. Accounting Non-Framed Access AVP Table . . . 80
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 80 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 82
11.1. Command Codes . . . . . . . . . . . . . . . . . . . . . 80 11.1. Command Codes . . . . . . . . . . . . . . . . . . . . . 82
11.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . 81 11.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . 83
11.3. Application Identifier . . . . . . . . . . . . . . . . 81 11.3. Application Identifier . . . . . . . . . . . . . . . . 83
11.4. CHAP-Algorithm AVP Values . . . . . . . . . . . . . . . 81 11.4. CHAP-Algorithm AVP Values . . . . . . . . . . . . . . . 83
11.5. Accounting-Auth-Method AVP Values . . . . . . . . . . . 81 11.5. Accounting-Auth-Method AVP Values . . . . . . . . . . . 83
12. Security Considerations . . . . . . . . . . . . . . . . . . . . 81 12. Security Considerations . . . . . . . . . . . . . . . . . . . . 83
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 82 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 84
13.1. Normative References . . . . . . . . . . . . . . . . . 82 13.1. Normative References . . . . . . . . . . . . . . . . . 84
13.2. Informative References . . . . . . . . . . . . . . . . 83 13.2. Informative References . . . . . . . . . . . . . . . . 85
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 85
15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 85 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 87
Intellectual Property Considerations . . . . . . . . . . . . . . . . 86 15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 88
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . . 86 Intellectual Property Considerations . . . . . . . . . . . . . . . . 89
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . . 89
1. Introduction 1. Introduction
This document describes the Diameter protocol application used for This document describes the Diameter protocol application used for
AAA in the Network Access Server (NAS) environment. This Diameter NAS AAA in the Network Access Server (NAS) environment. This Diameter NAS
application specification, when combined with the Diameter Base application specification, when combined with the Diameter Base
protocol [Base], Transport Profile [DiamTrans], and EAP [DiamEAP] protocol [Base], Transport Profile [DiamTrans], and EAP [DiamEAP]
specifications, satisfies NAS-related requirements defined in RFC2989 specifications, satisfies NAS-related requirements defined in RFC2989
[AAACriteria] and RFC3169 [NASCriteria]. [AAACriteria] and RFC3169 [NASCriteria].
Initial deployments of the Diameter protocol are expected to include Initial deployments of the Diameter protocol are expected to include
skipping to change at page 8, line 33 skipping to change at page 8, line 33
1.2. Requirements Language 1.2. Requirements Language
In this document, the key words "MAY", "MUST", "MUST NOT", In this document, the key words "MAY", "MUST", "MUST NOT",
"OPTIONAL", "RECOMMENDED", "SHOULD", and "SHOULD NOT", are to be "OPTIONAL", "RECOMMENDED", "SHOULD", and "SHOULD NOT", are to be
interpreted as described in [Keywords]. interpreted as described in [Keywords].
1.3. Advertising Application Support 1.3. Advertising Application Support
Diameter applications conforming to this specification MUST advertise Diameter applications conforming to this specification MUST advertise
support by including the value of one (1) in the Auth-Application-Id support by including the value of one (1) in the Auth-Application-Id
or the Acct-Application-Id AVP of the Capabilities-Exchange-Request of Capabilities-Exchange-Request (CER), AA-Request (AAR) and AA-
and Capabilities-Exchange-Answer commands [Base]. Answer (AAA) messages. All other messages are defined by [Base] and
use the Base application id value.
2. NAS Calls, Ports, and Sessions 2. NAS Calls, Ports, and Sessions
The arrival of a new call or service connection at a port of a The arrival of a new call or service connection at a port of a
Network Access Server (NAS) starts a Diameter NAS message exchange. Network Access Server (NAS) starts a Diameter NAS message exchange.
Information about the call, the identity of the user, and the user's Information about the call, the identity of the user, and the user's
authentication information are packaged into a Diameter AA-Request authentication information are packaged into a Diameter AA-Request
(AAR) message and sent to a server. (AAR) message and sent to a server.
The server processes the information and responds with a Diameter AA- The server processes the information and responds with a Diameter AA-
skipping to change at page 15, line 18 skipping to change at page 14, line 18
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ User-Name ] [ User-Name ]
[ Service-Type ] [ Service-Type ]
* [ Class ] * [ Class ]
* [ Configuration-Token ] * [ Configuration-Token ]
[ Acct-Interim-Interval ] [ Acct-Interim-Interval ]
[ Error-Message ] [ Error-Message ]
[ Error-Reporting-Host ] [ Error-Reporting-Host ]
* [ Failed-AVP ]
[ Idle-Timeout ] [ Idle-Timeout ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Grace-Period ] [ Auth-Grace-Period ]
[ Auth-Session-State ] [ Auth-Session-State ]
[ Re-Auth-Request-Type ] [ Re-Auth-Request-Type ]
[ Session-Timeout ] [ Session-Timeout ]
[ State ] [ State ]
* [ Reply-Message ] * [ Reply-Message ]
[ Origin-State-Id ] [ Origin-State-Id ]
* [ Filter-Id ] * [ Filter-Id ]
skipping to change at page 15, line 51 skipping to change at page 15, line 4
* [ Framed-Compression ] * [ Framed-Compression ]
[ Framed-Interface-Id ] [ Framed-Interface-Id ]
[ Framed-IP-Address ] [ Framed-IP-Address ]
* [ Framed-IPv6-Prefix ] * [ Framed-IPv6-Prefix ]
[ Framed-IPv6-Pool ] [ Framed-IPv6-Pool ]
* [ Framed-IPv6-Route ] * [ Framed-IPv6-Route ]
[ Framed-IP-Netmask ] [ Framed-IP-Netmask ]
* [ Framed-Route ] * [ Framed-Route ]
[ Framed-Pool ] [ Framed-Pool ]
[ Framed-IPX-Network ] [ Framed-IPX-Network ]
[ Framed-MTU ]
[ Framed-MTU ]
[ Framed-Protocol ] [ Framed-Protocol ]
[ Framed-Routing ] [ Framed-Routing ]
* [ Login-IP-Host ] * [ Login-IP-Host ]
* [ Login-IPv6-Host ] * [ Login-IPv6-Host ]
[ Login-LAT-Group ] [ Login-LAT-Group ]
[ Login-LAT-Node ] [ Login-LAT-Node ]
[ Login-LAT-Port ] [ Login-LAT-Port ]
[ Login-LAT-Service ] [ Login-LAT-Service ]
[ Login-Service ] [ Login-Service ]
[ Login-TCP-Port ] [ Login-TCP-Port ]
* [ NAS-Filter-Rule ] * [ NAS-Filter-Rule ]
* [ QoS-Filter-Rule ]
* [ Tunneling ] * [ Tunneling ]
* [ Redirect-Host ] * [ Redirect-Host ]
[ Redirect-Host-Usage ] [ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ] [ Redirect-Max-Cache-Time ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ AVP ] * [ AVP ]
3.3. Re-Auth-Request (RAR) Command 3.3. Re-Auth-Request (RAR) Command
A Diameter server may initiate a re-authentication and/or re- A Diameter server may initiate a re-authentication and/or re-
skipping to change at page 18, line 19 skipping to change at page 17, line 19
[ User-Name ] [ User-Name ]
[ Origin-State-Id ] [ Origin-State-Id ]
[ Error-Message ] [ Error-Message ]
[ Error-Reporting-Host ] [ Error-Reporting-Host ]
* [ Failed-AVP ] * [ Failed-AVP ]
* [ Redirected-Host ] * [ Redirected-Host ]
[ Redirected-Host-Usage ] [ Redirected-Host-Usage ]
[ Redirected-Host-Cache-Time ] [ Redirected-Host-Cache-Time ]
[ Service-Type ] [ Service-Type ]
* [ Configuration-Token ] * [ Configuration-Token ]
[ Error-Message ]
[ Error-Reporting-Host ]
[ Idle-Timeout ] [ Idle-Timeout ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Grace-Period ] [ Auth-Grace-Period ]
[ Re-Auth-Request-Type ] [ Re-Auth-Request-Type ]
[ State ] [ State ]
* [ Class ] * [ Class ]
* [ Reply-Message ] * [ Reply-Message ]
[ Prompt ] [ Prompt ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ AVP ] * [ AVP ]
skipping to change at page 23, line 7 skipping to change at page 22, line 7
[ Originating-Line-Info ] [ Originating-Line-Info ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Session-Timeout ] [ Session-Timeout ]
[ Idle-Timeout ] [ Idle-Timeout ]
[ Port-Limit ] [ Port-Limit ]
[ Accounting-Realtime-Required ] [ Accounting-Realtime-Required ]
[ Acct-Interim-Interval ] [ Acct-Interim-Interval ]
* [ Filter-Id ] * [ Filter-Id ]
* [ NAS-Filter-Rule ] * [ NAS-Filter-Rule ]
* [ Qos-Filter-Rule ]
[ Framed-AppleTalk-Link ] [ Framed-AppleTalk-Link ]
[ Framed-AppleTalk-Network ] [ Framed-AppleTalk-Network ]
[ Framed-AppleTalk-Zone ] [ Framed-AppleTalk-Zone ]
[ Framed-Compression ] [ Framed-Compression ]
[ Framed-Interface-Id ] [ Framed-Interface-Id ]
[ Framed-IP-Address ] [ Framed-IP-Address ]
[ Framed-IP-Netmask ] [ Framed-IP-Netmask ]
* [ Framed-IPv6-Prefix ] * [ Framed-IPv6-Prefix ]
[ Framed-IPv6-Pool ] [ Framed-IPv6-Pool ]
* [ Framed-IPv6-Route ] * [ Framed-IPv6-Route ]
skipping to change at page 24, line 22 skipping to change at page 23, line 23
{ Origin-Realm } { Origin-Realm }
{ Accounting-Record-Type } { Accounting-Record-Type }
{ Accounting-Record-Number } { Accounting-Record-Number }
[ Acct-Application-Id ] [ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ] [ Vendor-Specific-Application-Id ]
[ User-Name ] [ User-Name ]
[ Accounting-Sub-Session-Id ] [ Accounting-Sub-Session-Id ]
[ Acct-Session-Id ] [ Acct-Session-Id ]
[ Acct-Multi-Session-Id ] [ Acct-Multi-Session-Id ]
[ Event-Timestamp ] [ Event-Timestamp ]
[ Error-Message ]
[ Error-Reporting-Host ] [ Error-Reporting-Host ]
* [ Failed-AVP ]
[ Origin-State-Id ] [ Origin-State-Id ]
[ NAS-Identifier ] [ NAS-Identifier ]
[ NAS-IP-Address ] [ NAS-IP-Address ]
[ NAS-IPv6-Address ] [ NAS-IPv6-Address ]
[ NAS-Port ] [ NAS-Port ]
[ NAS-Port-Id ] [ NAS-Port-Id ]
[ NAS-Port-Type ] [ NAS-Port-Type ]
[ Service-Type ] [ Service-Type ]
[ Termination-Cause ] [ Termination-Cause ]
[ Accounting-Realtime-Required ] [ Accounting-Realtime-Required ]
skipping to change at page 31, line 23 skipping to change at page 30, line 29
The clear-text password (prior to encryption) MUST NOT be longer than The clear-text password (prior to encryption) MUST NOT be longer than
128 bytes in length. 128 bytes in length.
5.2. Password-Retry AVP 5.2. Password-Retry AVP
The Password-Retry AVP (AVP Code 75) is of type Unsigned32 and MAY be The Password-Retry AVP (AVP Code 75) is of type Unsigned32 and MAY be
included in the AA-Answer if the Result-Code indicates an included in the AA-Answer if the Result-Code indicates an
authentication failure. The value of this AVP indicates how many authentication failure. The value of this AVP indicates how many
authentication attempts a user may be permitted before being authentication attempts a user may be permitted before being
disconnected. This AVP is primarily intended for use when the Framed- disconnected. This AVP is primarily intended for use when the Framed-
Protocol AVP (see Section 6.9.1) is set to ARAP. Protocol AVP (see Section 6.10.1) is set to ARAP.
5.3. Prompt AVP 5.3. Prompt AVP
The Prompt AVP (AVP Code 76) is of type Enumerated, and MAY be The Prompt AVP (AVP Code 76) is of type Enumerated, and MAY be
present in the AA-Answer message. When present, it is used by the NAS present in the AA-Answer message. When present, it is used by the NAS
to determine whether the user's response, when entered, should be to determine whether the user's response, when entered, should be
echoed. echoed.
The supported values are listed in [RADIUSTypes]. The following list The supported values are listed in [RADIUSTypes]. The following list
is informational: is informational:
skipping to change at page 32, line 43 skipping to change at page 31, line 46
5.8. CHAP-Challenge AVP 5.8. CHAP-Challenge AVP
The CHAP-Challenge AVP (AVP Code 60) is of type OctetString and The CHAP-Challenge AVP (AVP Code 60) is of type OctetString and
contains the CHAP Challenge sent by the NAS to the CHAP peer contains the CHAP Challenge sent by the NAS to the CHAP peer
[PPPCHAP]. [PPPCHAP].
5.9. ARAP-Password AVP 5.9. ARAP-Password AVP
The ARAP-Password AVP (AVP Code 70) is of type OctetString and is The ARAP-Password AVP (AVP Code 70) is of type OctetString and is
only present when the Framed-Protocol AVP (see Section 6.9.1) is only present when the Framed-Protocol AVP (see Section 6.10.1) is
included in the message and is set to ARAP. This AVP MUST NOT be included in the message and is set to ARAP. This AVP MUST NOT be
present if either the User-Password or the CHAP-Auth AVP is present. present if either the User-Password or the CHAP-Auth AVP is present.
See [RADIUSExt] for more information on the contents of this AVP. See [RADIUSExt] for more information on the contents of this AVP.
5.10. ARAP-Challenge-Response AVP 5.10. ARAP-Challenge-Response AVP
The ARAP-Challenge-Response AVP (AVP Code 84) is of type OctetString The ARAP-Challenge-Response AVP (AVP Code 84) is of type OctetString
and is only present when the Framed-Protocol AVP (see Section 6.9.1) and is only present when the Framed-Protocol AVP (see Section 6.10.1)
is included in the message and is set to ARAP. This AVP contains an 8 is included in the message and is set to ARAP. This AVP contains an 8
octet response to the dial-in client's challenge. The RADIUS server octet response to the dial-in client's challenge. The RADIUS server
calculates this value by taking the dial-in client's challenge from calculates this value by taking the dial-in client's challenge from
the high order 8 octets of the ARAP-Password AVP and performing DES the high order 8 octets of the ARAP-Password AVP and performing DES
encryption on this value with the authenticating user's password as encryption on this value with the authenticating user's password as
the key. If the user's password is less than 8 octets in length, the the key. If the user's password is less than 8 octets in length, the
password is padded at the end with NULL octets to a length of 8 password is padded at the end with NULL octets to a length of 8
before using it as a key. before using it as a key.
5.11. ARAP-Security AVP 5.11. ARAP-Security AVP
The ARAP-Security AVP (AVP Code 73) is of type Unsigned32, and MAY be The ARAP-Security AVP (AVP Code 73) is of type Unsigned32, and MAY be
present in the AA-Answer message if the Framed-Protocol AVP (see present in the AA-Answer message if the Framed-Protocol AVP (see
Section 6.9.1) is set to the value of ARAP, and the Result-Code AVP Section 6.10.1) is set to the value of ARAP, and the Result-Code AVP
is set to DIAMETER_MULTI_ROUND_AUTH. See [RADIUSExt] for more is set to DIAMETER_MULTI_ROUND_AUTH. See [RADIUSExt] for more
information on the format of this AVP. information on the format of this AVP.
5.12. ARAP-Security-Data AVP 5.12. ARAP-Security-Data AVP
The ARAP-Security AVP (AVP Code 74) is of type OctetString, and MAY The ARAP-Security AVP (AVP Code 74) is of type OctetString, and MAY
be present in the AA-Request or AA-Answer message if the Framed- be present in the AA-Request or AA-Answer message if the Framed-
Protocol AVP is set to the value of ARAP, and the Result-Code AVP is Protocol AVP is set to the value of ARAP, and the Result-Code AVP is
set to DIAMETER_MULTI_ROUND_AUTH. This AVP contains the security set to DIAMETER_MULTI_ROUND_AUTH. This AVP contains the security
module challenge or response associated with the ARAP Security Module module challenge or response associated with the ARAP Security Module
specified in ARAP-Security. specified in ARAP-Security.
6. NAS Authorization AVPs 6. NAS Authorization AVPs
This section contains the authorization AVPs that are supported in This section contains the authorization AVPs that are supported in
the NAS Application. The Service-Type AVP SHOULD be present in all the NAS Application. The Service-Type AVP SHOULD be present in all
messages, and based on its value, additional AVPs defined in this messages, and based on its value, additional AVPs defined in this
section and section 7 MAY be present. section and section 7 MAY be present.
Due to space constraints, the short form IPFiltrRule is used to Due to space constraints, the short form IPFltrRule is used to
represent IPFilterRule. represent IPFilterRule, and QoSFltrRule for QoSFilterRule
+---------------------+ +---------------------+
| AVP Flag rules | | AVP Flag rules |
|----+-----+----+-----|----+ |----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| | AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr| Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----| -----------------------------------------|----+-----+----+-----|----|
Service-Type 6 6.1 Enumerated | M | P | | V | Y | Service-Type 6 6.1 Enumerated | M | P | | V | Y |
Callback-Number 19 6.2 UTF8String | M | P | | V | Y | Callback-Number 19 6.2 UTF8String | M | P | | V | Y |
Callback-Id 20 6.3 UTF8String | M | P | | V | Y | Callback-Id 20 6.3 UTF8String | M | P | | V | Y |
Idle-Timeout 28 6.4 Unsigned32 | M | P | | V | Y | Idle-Timeout 28 6.4 Unsigned32 | M | P | | V | Y |
Port-Limit 62 6.5 Unsigned32 | M | P | | V | Y | Port-Limit 62 6.5 Unsigned32 | M | P | | V | Y |
NAS-Filter-Rule 400 6.6 IPFiltrRule| M | P | | V | Y | NAS-Filter-Rule 400 6.6 IPFltrRule | M | P | | V | Y |
Filter-Id 11 6.7 UTF8String | M | P | | V | Y | Filter-Id 11 6.7 UTF8String | M | P | | V | Y |
Configuration- 78 6.8 OctetString| M | | | P,V | | Configuration- 78 6.8 OctetString| M | | | P,V | |
Token | | | | | | Token | | | | | |
Framed-Protocol 7 6.9.1 Enumerated | M | P | | V | Y | QoS-Filter-Rule 407 6.9 QoSFltrRule| | | | | |
Framed-Routing 10 6.9.2 Enumerated | M | P | | V | Y | Framed-Protocol 7 6.10.1 Enumerated | M | P | | V | Y |
Framed-MTU 12 6.9.3 Unsigned32 | M | P | | V | Y | Framed-Routing 10 6.10.2 Enumerated | M | P | | V | Y |
Framed- 13 6.9.4 Enumerated | M | P | | V | Y | Framed-MTU 12 6.10.3 Unsigned32 | M | P | | V | Y |
Framed- 13 6.10.4 Enumerated | M | P | | V | Y |
Compression | | | | | | Compression | | | | | |
Framed-IP-Address 8 6.10.1 OctetString| M | P | | V | Y | Framed-IP-Address 8 6.11.1 OctetString| M | P | | V | Y |
Framed-IP-Netmask 9 6.10.2 OctetString| M | P | | V | Y | Framed-IP-Netmask 9 6.11.2 OctetString| M | P | | V | Y |
Framed-Route 22 6.10.3 UTF8String | M | P | | V | Y | Framed-Route 22 6.11.3 UTF8String | M | P | | V | Y |
Framed-Pool 88 6.10.4 OctetString| M | P | | V | Y | Framed-Pool 88 6.11.4 OctetString| M | P | | V | Y |
Framed- 96 6.10.5 Unsigned64 | M | P | | V | Y | Framed- 96 6.11.5 Unsigned64 | M | P | | V | Y |
Interface-Id | | | | | | Interface-Id | | | | | |
Framed-IPv6- 97 6.10.6 OctetString| M | P | | V | Y | Framed-IPv6- 97 6.11.6 OctetString| M | P | | V | Y |
Prefix | | | | | | Prefix | | | | | |
Framed-IPv6- 99 6.10.7 UTF8String | M | P | | V | Y | Framed-IPv6- 99 6.11.7 UTF8String | M | P | | V | Y |
Route | | | | | | Route | | | | | |
Framed-IPv6-Pool 100 6.10.8 OctetString| M | P | | V | Y | Framed-IPv6-Pool 100 6.11.8 OctetString| M | P | | V | Y |
Framed-IPX- 23 6.11.1 UTF8String | M | P | | V | Y | Framed-IPX- 23 6.12.1 UTF8String | M | P | | V | Y |
Network | | | | | | Network | | | | | |
Framed-Appletalk- 37 6.12.1 Unsigned32 | M | P | | V | Y | Framed-Appletalk- 37 6.13.1 Unsigned32 | M | P | | V | Y |
Link | | | | | | Link | | | | | |
Framed-Appletalk- 38 6.12.2 Unsigned32 | M | P | | V | Y | Framed-Appletalk- 38 6.13.2 Unsigned32 | M | P | | V | Y |
Network | | | | | | Network | | | | | |
Framed-Appletalk- 39 6.12.3 OctetString| M | P | | V | Y | Framed-Appletalk- 39 6.13.3 OctetString| M | P | | V | Y |
Zone | | | | | | Zone | | | | | |
ARAP-Features 71 6.13.1 OctetString| M | P | | V | Y | ARAP-Features 71 6.14.1 OctetString| M | P | | V | Y |
ARAP-Zone-Access 72 6.13.2 Enumerated | M | P | | V | Y | ARAP-Zone-Access 72 6.14.2 Enumerated | M | P | | V | Y |
Login-IP-Host 14 6.14.1 OctetString| M | P | | V | Y | Login-IP-Host 14 6.15.1 OctetString| M | P | | V | Y |
Login-IPv6-Host 98 6.14.2 OctetString| M | P | | V | Y | Login-IPv6-Host 98 6.15.2 OctetString| M | P | | V | Y |
Login-Service 15 6.14.3 Enumerated | M | P | | V | Y | Login-Service 15 6.15.3 Enumerated | M | P | | V | Y |
Login-TCP-Port 16 6.15.1 Unsigned32 | M | P | | V | Y | Login-TCP-Port 16 6.16.1 Unsigned32 | M | P | | V | Y |
Login-LAT-Service 34 6.16.1 OctetString| M | P | | V | Y | Login-LAT-Service 34 6.17.1 OctetString| M | P | | V | Y |
Login-LAT-Node 35 6.16.2 OctetString| M | P | | V | Y | Login-LAT-Node 35 6.17.2 OctetString| M | P | | V | Y |
Login-LAT-Group 36 6.16.3 OctetString| M | P | | V | Y | Login-LAT-Group 36 6.17.3 OctetString| M | P | | V | Y |
Login-LAT-Port 63 6.16.4 OctetString| M | P | | V | Y | Login-LAT-Port 63 6.17.4 OctetString| M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----| -----------------------------------------|----+-----+----+-----|----|
6.1. Service-Type AVP 6.1. Service-Type AVP
The Service-Type AVP (AVP Code 6) is of type Enumerated and contains The Service-Type AVP (AVP Code 6) is of type Enumerated and contains
the type of service the user has requested, or the type of service to the type of service the user has requested, or the type of service to
be provided. One such AVP MAY be present in an authentication and/or be provided. One such AVP MAY be present in an authentication and/or
authorization request or response. A NAS is not required to implement authorization request or response. A NAS is not required to implement
all of these service types, and MUST treat unknown or unsupported all of these service types, and MUST treat unknown or unsupported
Service-Types received in a response as a failure, and end the Service-Types received in a response as a failure, and end the
skipping to change at page 36, line 4 skipping to change at page 35, line 5
13 Fax 13 Fax
14 Modem Relay 14 Modem Relay
15 IAPP-Register [IEEE 802.11f] 15 IAPP-Register [IEEE 802.11f]
16 IAPP-AP-Check [IEEE 802.11f] 16 IAPP-AP-Check [IEEE 802.11f]
17 Authorize Only [RFC3576] 17 Authorize Only [RFC3576]
The following values are further qualified: The following values are further qualified:
Login 1 Login 1
The user should be connected to a host. The message MAY include The user should be connected to a host. The message MAY include
additional AVPs defined in sections 6.15 or 6.16. additional AVPs defined in sections 6.16 or 6.17.
Framed 2 Framed 2
A Framed Protocol should be started for the User, such as PPP A Framed Protocol should be started for the User, such as PPP
or SLIP. The message MAY include additional AVPs defined in or SLIP. The message MAY include additional AVPs defined in
sections 6.9, or 7 for tunneling services. sections 6.10, or 7 for tunneling services.
Callback Login 3 Callback Login 3
The user should be disconnected and called back, then connected The user should be disconnected and called back, then connected
to a host. The message MAY include additional AVPs defined in to a host. The message MAY include additional AVPs defined in
this section. this section.
Callback Framed 4 Callback Framed 4
The user should be disconnected and called back, then a Framed The user should be disconnected and called back, then a Framed
Protocol should be started for the User, such as PPP or SLIP. Protocol should be started for the User, such as PPP or SLIP.
The message MAY include additional AVPs defined in sections The message MAY include additional AVPs defined in sections
6.9, or 7 for tunneling services. 6.10, or 7 for tunneling services.
6.2. Callback-Number AVP 6.2. Callback-Number AVP
The Callback-Number AVP (AVP Code 19) is of type UTF8String, and The Callback-Number AVP (AVP Code 19) is of type UTF8String, and
contains a dialing string to be used for callback. It MAY be used in contains a dialing string to be used for callback. It MAY be used in
an authentication and/or authorization request as a hint to the an authentication and/or authorization request as a hint to the
server that a Callback service is desired, but the server is not server that a Callback service is desired, but the server is not
required to honor the hint in the corresponding response. required to honor the hint in the corresponding response.
The codification of the range of allowed usage of this field is The codification of the range of allowed usage of this field is
skipping to change at page 38, line 5 skipping to change at page 37, line 5
6.8. Configuration-Token AVP 6.8. Configuration-Token AVP
The Configuration-Token AVP (AVP Code 78) is of type OctetString and The Configuration-Token AVP (AVP Code 78) is of type OctetString and
is sent by a Diameter Server to a Diameter Proxy Agent or Translation is sent by a Diameter Server to a Diameter Proxy Agent or Translation
Agent in an AA-Answer command to indicate a type of user profile to Agent in an AA-Answer command to indicate a type of user profile to
be used. It should not be sent to a Diameter Client (NAS). be used. It should not be sent to a Diameter Client (NAS).
The format of the Data field of this AVP is site specific. The format of the Data field of this AVP is site specific.
6.9. Framed Access Authorization AVPs 6.9. QoS-Filter-Rule AVP
The QoS-Filter-Rule AVP (AVP Code 407) is of type QoSFilterRule, and
provides QoS filter rules that need to be configured on the NAS for
the user. One or more such AVPs MAY be present in an authorization
response.
Note: Due to an editorial mistake in [Base], only the AVP format is
discussed. The complete QoSFilterRule definition was not included.
It is reprinted here for clarification.
QoSFilterRule
The QosFilterRule format is derived from the OctetString AVP Base
Format. It uses the ASCII charset. Packets may be marked or
metered based on the following information that is associated with
it:
Direction (in or out)
Source and destination IP address (possibly masked)
Protocol
Source and destination port (lists or ranges)
DSCP values (no mask or range)
Rules for the appropriate direction are evaluated in order, with
the first matched rule terminating the evaluation. Each packet is
evaluated once. If no rule matches, the packet is treated as best
effort. An access device that is unable to interpret or apply a
QoS rule SHOULD NOT terminate the session.
QoSFilterRule filters MUST follow the format:
action dir proto from src to dst [options]
tag - Mark packet with a specific DSCP
[DIFFSERV]. The DSCP option MUST be
included.
meter - Meter traffic. The metering options
MUST be included.
dir The format is as described under IPFilterRule.
proto The format is as described under IPFilterRule.
src and dst The format is as described under IPFilterRule.
options:
DSCP <color>
color values as defined in [DIFFSERV]. Exact
matching of DSCP values is required (no masks or
ranges).
metering <rate> <color_under> <color_over>
The metering option provides Assured Forwarding,
as defined in [DIFFSERVAF], and MUST be present
if the action is set to meter. The rate option is
the throughput, in bits per second, which is used
by the access device to mark packets. Traffic
above the rate is marked with the color_over
codepoint, while traffic under the rate is marked
with the color_under codepoint. The color_under
and color_over options contain the drop
preferences, and MUST conform to the recommended
codepoint keywords described in [DIFFSERVAF]
(e.g. AF13).
The metering option also supports the strict
limit on traffic required by Expedited
Forwarding, as defined in [DIFFSERVEF]. The
color_over option may contain the keyword "drop"
to prevent forwarding of traffic that exceeds the
rate parameter.
The rule syntax is a modified subset of ipfw(8) from FreeBSD,
and the ipfw.c code may provide a useful base for
implementations.
6.10. Framed Access Authorization AVPs
This section contains the authorization AVPs that are necessary to This section contains the authorization AVPs that are necessary to
support framed access, such as PPP, SLIP, etc. AVPs defined in this support framed access, such as PPP, SLIP, etc. AVPs defined in this
section MAY be present in a message if the Service-Type AVP was set section MAY be present in a message if the Service-Type AVP was set
to "Framed" or "Callback Framed". to "Framed" or "Callback Framed".
6.9.1. Framed-Protocol AVP 6.10.1. Framed-Protocol AVP
The Framed-Protocol AVP (AVP Code 7) is of type Enumerated and The Framed-Protocol AVP (AVP Code 7) is of type Enumerated and
contains the framing to be used for framed access. This AVP MAY be contains the framing to be used for framed access. This AVP MAY be
present in both requests and responses. The supported values are present in both requests and responses. The supported values are
listed in [RADIUSTypes]. The following list is informational: listed in [RADIUSTypes]. The following list is informational:
1 PPP 1 PPP
2 SLIP 2 SLIP
3 AppleTalk Remote Access Protocol (ARAP) 3 AppleTalk Remote Access Protocol (ARAP)
4 Gandalf proprietary SingleLink/MultiLink protocol 4 Gandalf proprietary SingleLink/MultiLink protocol
5 Xylogics proprietary IPX/SLIP 5 Xylogics proprietary IPX/SLIP
6 X.75 Synchronous 6 X.75 Synchronous
6.9.2. Framed-Routing AVP 6.10.2. Framed-Routing AVP
The Framed-Routing AVP (AVP Code 10) is of type Enumerated and The Framed-Routing AVP (AVP Code 10) is of type Enumerated and
contains the routing method for the user, when the user is a router contains the routing method for the user, when the user is a router
to a network. This AVP SHOULD only be present in authorization to a network. This AVP SHOULD only be present in authorization
responses. The supported values are listed in [RADIUSTypes]. The responses. The supported values are listed in [RADIUSTypes]. The
following list is informational: following list is informational:
0 None 0 None
1 Send routing packets 1 Send routing packets
2 Listen for routing packets 2 Listen for routing packets
3 Send and Listen 3 Send and Listen
6.9.3. Framed-MTU AVP 6.10.3. Framed-MTU AVP
The Framed-MTU AVP (AVP Code 12) is of type Unsigned32 and contains The Framed-MTU AVP (AVP Code 12) is of type Unsigned32 and contains
the Maximum Transmission Unit to be configured for the user, when it the Maximum Transmission Unit to be configured for the user, when it
is not negotiated by some other means (such as PPP). This AVP SHOULD is not negotiated by some other means (such as PPP). This AVP SHOULD
only be present in authorization responses. The MTU value MUST be in only be present in authorization responses. The MTU value MUST be in
the range of 64 and 65535. the range of 64 and 65535.
6.9.4. Framed-Compression AVP 6.10.4. Framed-Compression AVP
The Framed-Compression AVP (AVP Code 13) is of type Enumerated and The Framed-Compression AVP (AVP Code 13) is of type Enumerated and
contains the compression protocol to be used for the link. It MAY be contains the compression protocol to be used for the link. It MAY be
used in an authorization request as a hint to the server that a used in an authorization request as a hint to the server that a
specific compression type is desired, but the server is not required specific compression type is desired, but the server is not required
to honor the hint in the corresponding response. to honor the hint in the corresponding response.
More than one compression protocol AVP MAY be sent. It is the More than one compression protocol AVP MAY be sent. It is the
responsibility of the NAS to apply the proper compression protocol to responsibility of the NAS to apply the proper compression protocol to
appropriate link traffic. appropriate link traffic.
The supported values are listed in [RADIUSTypes]. The following list The supported values are listed in [RADIUSTypes]. The following list
is informational: is informational:
0 None 0 None
1 VJ TCP/IP header compression 1 VJ TCP/IP header compression
2 IPX header compression 2 IPX header compression
3 Stac-LZS compression 3 Stac-LZS compression
6.10. IP Access Authorization AVPs 6.11. IP Access Authorization AVPs
The AVPs defined in this section are used when the user requests, or The AVPs defined in this section are used when the user requests, or
is being granted, access service to IP. is being granted, access service to IP.
6.10.1. Framed-IP-Address AVP 6.11.1. Framed-IP-Address AVP
The Framed-IP-Address AVP (AVP Code 8) [RADIUS] is of type The Framed-IP-Address AVP (AVP Code 8) [RADIUS] is of type
OctetString and contains an IPv4 address, of the type specified in OctetString and contains an IPv4 address, of the type specified in
the attribute value, to be configured for the user. It MAY be used in the attribute value, to be configured for the user. It MAY be used in
an authorization request as a hint to the server that a specific an authorization request as a hint to the server that a specific
address is desired, but the server is not required to honor the hint address is desired, but the server is not required to honor the hint
in the corresponding response. in the corresponding response.
Two values have special significance; 0xFFFFFFFF and 0xFFFFFFFE. The Two values have special significance; 0xFFFFFFFF and 0xFFFFFFFE. The
value 0xFFFFFFFF indicates that the NAS should allow the user to value 0xFFFFFFFF indicates that the NAS should allow the user to
select an address (e.g. Negotiated). The value 0xFFFFFFFE indicates select an address (e.g. Negotiated). The value 0xFFFFFFFE indicates
that the NAS should select an address for the user (e.g. Assigned that the NAS should select an address for the user (e.g. Assigned
from a pool of addresses kept by the NAS). from a pool of addresses kept by the NAS).
6.10.2. Framed-IP-Netmask AVP 6.11.2. Framed-IP-Netmask AVP
The Framed-IP-Netmask AVP (AVP Code 9) is of type OctetString and The Framed-IP-Netmask AVP (AVP Code 9) is of type OctetString and
contains the four octets of the IPv4 netmask to be configured for the contains the four octets of the IPv4 netmask to be configured for the
user when the user is a router to a network. It MAY be used in an user when the user is a router to a network. It MAY be used in an
authorization request as a hint to the server that a specific netmask authorization request as a hint to the server that a specific netmask
is desired, but the server is not required to honor the hint in the is desired, but the server is not required to honor the hint in the
corresponding response. This AVP MUST be present in a response if the corresponding response. This AVP MUST be present in a response if the
request included this AVP with a value of 0xFFFFFFFF. request included this AVP with a value of 0xFFFFFFFF.
6.10.3. Framed-Route AVP 6.11.3. Framed-Route AVP
The Framed-Route AVP (AVP Code 22) is of type UTF8String, and The Framed-Route AVP (AVP Code 22) is of type UTF8String, and
contains the ASCII routing information to be configured for the user contains the ASCII routing information to be configured for the user
on the NAS. Zero or more such AVPs MAY be present in an authorization on the NAS. Zero or more such AVPs MAY be present in an authorization
response. response.
The string MUST contain a destination prefix in dotted quad form The string MUST contain a destination prefix in dotted quad form
optionally followed by a slash and a decimal length specifier stating optionally followed by a slash and a decimal length specifier stating
how many high order bits of the prefix should be used. That is how many high order bits of the prefix should be used. That is
followed by a space, a gateway address in dotted quad form, a space, followed by a space, a gateway address in dotted quad form, a space,
and one or more metrics separated by spaces. For example, and one or more metrics separated by spaces. For example,
"192.168.1.0/24 192.168.1.1 1". "192.168.1.0/24 192.168.1.1 1".
The length specifier may be omitted in which case it should default The length specifier may be omitted in which case it should default
to 8 bits for class A prefixes, 16 bits for class B prefixes, and 24 to 8 bits for class A prefixes, 16 bits for class B prefixes, and 24
bits for class C prefixes. For example, "192.168.1.0 192.168.1.1 1". bits for class C prefixes. For example, "192.168.1.0 192.168.1.1 1".
Whenever the gateway address is specified as "0.0.0.0" the IP address Whenever the gateway address is specified as "0.0.0.0" the IP address
of the user SHOULD be used as the gateway address. of the user SHOULD be used as the gateway address.
6.10.4. Framed-Pool AVP 6.11.4. Framed-Pool AVP
The Framed-Pool AVP (AVP Code 88) is of type OctetString and contains The Framed-Pool AVP (AVP Code 88) is of type OctetString and contains
the name of an assigned address pool that SHOULD be used to assign an the name of an assigned address pool that SHOULD be used to assign an
address for the user. If a NAS does not support multiple address address for the user. If a NAS does not support multiple address
pools, the NAS SHOULD ignore this AVP. Address pools are usually pools, the NAS SHOULD ignore this AVP. Address pools are usually
used for IP addresses, but can be used for other protocols if the NAS used for IP addresses, but can be used for other protocols if the NAS
supports pools for those protocols. supports pools for those protocols.
Although specified as type OctetString for compatibility with RADIUS Although specified as type OctetString for compatibility with RADIUS
[RADIUSExt], the encoding of the Data field SHOULD also conform to [RADIUSExt], the encoding of the Data field SHOULD also conform to
the rules for the UTF8String Data Format. the rules for the UTF8String Data Format.
6.10.5. Framed-Interface-Id AVP 6.11.5. Framed-Interface-Id AVP
The Framed-Interface-Id AVP (AVP Code 96) is of type Unsigned64 and The Framed-Interface-Id AVP (AVP Code 96) is of type Unsigned64 and
contains the IPv6 interface identifier to be configured for the user. contains the IPv6 interface identifier to be configured for the user.
It MAY be used in authorization requests as a hint to the server that It MAY be used in authorization requests as a hint to the server that
a specific interface id is desired, but the server is not required to a specific interface id is desired, but the server is not required to
honor the hint in the corresponding response. honor the hint in the corresponding response.
6.10.6. Framed-IPv6-Prefix AVP 6.11.6. Framed-IPv6-Prefix AVP
The Framed-IPv6-Prefix AVP (AVP Code 97) is of type OctetString and The Framed-IPv6-Prefix AVP (AVP Code 97) is of type OctetString and
contains the IPv6 prefix to be configured for the user. One or more contains the IPv6 prefix to be configured for the user. One or more
AVPs MAY be used in authorization requests as a hint to the server AVPs MAY be used in authorization requests as a hint to the server
that a specific IPv6 prefixes are desired, but the server is not that a specific IPv6 prefixes are desired, but the server is not
required to honor the hint in the corresponding response. required to honor the hint in the corresponding response.
6.10.7. Framed-IPv6-Route AVP 6.11.7. Framed-IPv6-Route AVP
The Framed-IPv6-Route AVP (AVP Code 99) is of type UTF8String, and The Framed-IPv6-Route AVP (AVP Code 99) is of type UTF8String, and
contains the ASCII routing information to be configured for the user contains the ASCII routing information to be configured for the user
on the NAS. Zero or more such AVPs MAY be present in an authorization on the NAS. Zero or more such AVPs MAY be present in an authorization
response. response.
The string MUST contain an IPv6 address prefix followed by a slash The string MUST contain an IPv6 address prefix followed by a slash
and a decimal length specifier stating how many high order bits of and a decimal length specifier stating how many high order bits of
the prefix should be used. That is followed by a space, a gateway the prefix should be used. That is followed by a space, a gateway
address in hexadecimal notation, a space, and one or more metrics address in hexadecimal notation, a space, and one or more metrics
separated by spaces. For example: separated by spaces. For example:
"2000:0:0:106::/64 2000::106:a00:20ff:fe99:a998 1". "2000:0:0:106::/64 2000::106:a00:20ff:fe99:a998 1".
Whenever the gateway address is the IPv6 unspecified address the IP Whenever the gateway address is the IPv6 unspecified address the IP
address of the user SHOULD be used as the gateway address, such as: address of the user SHOULD be used as the gateway address, such as:
"2000:0:0:106::/64 :: 1". "2000:0:0:106::/64 :: 1".
6.10.8. Framed-IPv6-Pool AVP 6.11.8. Framed-IPv6-Pool AVP
The Framed-IPv6-Pool AVP (AVP Code 100) is of type OctetString, and The Framed-IPv6-Pool AVP (AVP Code 100) is of type OctetString, and
contains the name of an assigned pool that SHOULD be used to assign contains the name of an assigned pool that SHOULD be used to assign
an IPv6 prefix for the user. If the access device does not support an IPv6 prefix for the user. If the access device does not support
multiple prefix pools, it MUST ignore this AVP. multiple prefix pools, it MUST ignore this AVP.
Although specified as type OctetString for compatibility with RADIUS Although specified as type OctetString for compatibility with RADIUS
[RADIUSIPv6], the encoding of the Data field SHOULD also conform to [RADIUSIPv6], the encoding of the Data field SHOULD also conform to
the rules for the UTF8String Data Format. the rules for the UTF8String Data Format.
6.11. IPX Access 6.12. IPX Access
The AVPs defined in this section are used when the user requests, or The AVPs defined in this section are used when the user requests, or
is being granted, access to an IPX network service. is being granted, access to an IPX network service.
6.11.1. Framed-IPX-Network AVP 6.12.1. Framed-IPX-Network AVP
The Framed-IPX-Network AVP (AVP Code 23) is of type Unsigned32, and The Framed-IPX-Network AVP (AVP Code 23) is of type Unsigned32, and
contains the IPX Network number to be configured for the user. It MAY contains the IPX Network number to be configured for the user. It MAY
be used in an authorization request as a hint to the server that a be used in an authorization request as a hint to the server that a
specific address is desired, but the server is not required to honor specific address is desired, but the server is not required to honor
the hint in the corresponding response. the hint in the corresponding response.
Two addresses have special significance; 0xFFFFFFFF and 0xFFFFFFFE. Two addresses have special significance; 0xFFFFFFFF and 0xFFFFFFFE.
The value 0xFFFFFFFF indicates that the NAS should allow the user to The value 0xFFFFFFFF indicates that the NAS should allow the user to
select an address (e.g. Negotiated). The value 0xFFFFFFFE indicates select an address (e.g. Negotiated). The value 0xFFFFFFFE indicates
that the NAS should select an address for the user (e.g. assigned that the NAS should select an address for the user (e.g. assigned
from a pool of one or more IPX networks kept by the NAS). from a pool of one or more IPX networks kept by the NAS).
6.12. AppleTalk Network Access 6.13. AppleTalk Network Access
The AVPs defined in this section are used when the user requests, or The AVPs defined in this section are used when the user requests, or
is being granted, access to an AppleTalk network [AppleTalk]. is being granted, access to an AppleTalk network [AppleTalk].
6.12.1. Framed-AppleTalk-Link AVP 6.13.1. Framed-AppleTalk-Link AVP
The Framed-AppleTalk-Link AVP (AVP Code 37) is of type Unsigned32 and The Framed-AppleTalk-Link AVP (AVP Code 37) is of type Unsigned32 and
contains the AppleTalk network number which should be used for the contains the AppleTalk network number which should be used for the
serial link to the user, which is another AppleTalk router. This AVP serial link to the user, which is another AppleTalk router. This AVP
MUST only be present in an authorization response and is never used MUST only be present in an authorization response and is never used
when the user is not another router. when the user is not another router.
Despite the size of the field, values range from zero to 65535. The Despite the size of the field, values range from zero to 65535. The
special value of zero indicates that this is an unnumbered serial special value of zero indicates that this is an unnumbered serial
link. A value of one to 65535 means that the serial line between the link. A value of one to 65535 means that the serial line between the
NAS and the user should be assigned that value as an AppleTalk NAS and the user should be assigned that value as an AppleTalk
network number. network number.
6.12.2. Framed-AppleTalk-Network AVP 6.13.2. Framed-AppleTalk-Network AVP
The Framed-AppleTalk-Network AVP (AVP Code 38) is of type Unsigned32 The Framed-AppleTalk-Network AVP (AVP Code 38) is of type Unsigned32
and contains the AppleTalk Network number which the NAS should probe and contains the AppleTalk Network number which the NAS should probe
to allocate an AppleTalk node for the user. This AVP MUST only be to allocate an AppleTalk node for the user. This AVP MUST only be
present in an authorization response and is never used when the user present in an authorization response and is never used when the user
is not another router. Multiple instances of this AVP indicate that is not another router. Multiple instances of this AVP indicate that
the NAS may probe using any of the network numbers specified. the NAS may probe using any of the network numbers specified.
Despite the size of the field, values range from zero to 65535. The Despite the size of the field, values range from zero to 65535. The
special value zero indicates that the NAS should assign a network for special value zero indicates that the NAS should assign a network for
the user, using its default cable range. A value between one and the user, using its default cable range. A value between one and
65535 (inclusive) indicates the AppleTalk Network the NAS should 65535 (inclusive) indicates the AppleTalk Network the NAS should
probe to find an address for the user. probe to find an address for the user.
6.12.3. Framed-AppleTalk-Zone AVP 6.13.3. Framed-AppleTalk-Zone AVP
The Framed-AppleTalk-Zone AVP (AVP Code 39) is of type OctetString The Framed-AppleTalk-Zone AVP (AVP Code 39) is of type OctetString
and contains the AppleTalk Default Zone to be used for this user. and contains the AppleTalk Default Zone to be used for this user.
This AVP MUST only be present in an authorization response. Multiple This AVP MUST only be present in an authorization response. Multiple
instances of this AVP in the same message are not allowed. instances of this AVP in the same message are not allowed.
The codification of the range of allowed usage of this field is The codification of the range of allowed usage of this field is
outside the scope of this specification. outside the scope of this specification.
6.13. AppleTalk Remote Access 6.14. AppleTalk Remote Access
The AVPs defined in this section are used when the user requests, or The AVPs defined in this section are used when the user requests, or
is being granted, access to the AppleTalk network via the AppleTalk is being granted, access to the AppleTalk network via the AppleTalk
Remote Access Protocol [ARAP]. They are only present if the Framed- Remote Access Protocol [ARAP]. They are only present if the Framed-
Protocol AVP (see Section 6.9.1) is set to ARAP. Section 2.2 of RFC Protocol AVP (see Section 6.10.1) is set to ARAP. Section 2.2 of RFC
2869 [RADIUSExt] describes the operational use of these attributes. 2869 [RADIUSExt] describes the operational use of these attributes.
6.13.1. ARAP-Features AVP 6.14.1. ARAP-Features AVP
The ARAP-Features AVP (AVP Code 71) is of type OctetString, and MAY The ARAP-Features AVP (AVP Code 71) is of type OctetString, and MAY
be present in the AA-Accept message if the Framed-Protocol AVP is set be present in the AA-Accept message if the Framed-Protocol AVP is set
to the value of ARAP. See [RADIUSExt] for more information of the to the value of ARAP. See [RADIUSExt] for more information of the
format of this AVP. format of this AVP.
6.13.2. ARAP-Zone-Access AVP 6.14.2. ARAP-Zone-Access AVP
The ARAP-Zone-Access AVP (AVP Code 72) is of type Enumerated, and MAY The ARAP-Zone-Access AVP (AVP Code 72) is of type Enumerated, and MAY
be present in the AA-Accept message if the Framed-Protocol AVP is set be present in the AA-Accept message if the Framed-Protocol AVP is set
to the value of ARAP. to the value of ARAP.
The supported values are listed in [RADIUSTypes], and are defined in The supported values are listed in [RADIUSTypes], and are defined in
[RADIUSExt]. [RADIUSExt].
6.14. Non-Framed Access Authorization AVPs 6.15. Non-Framed Access Authorization AVPs
This section contains the authorization AVPs that are needed to This section contains the authorization AVPs that are needed to
support terminal server functionality. AVPs defined in this section support terminal server functionality. AVPs defined in this section
MAY be present in a message if the Service-Type AVP was set to MAY be present in a message if the Service-Type AVP was set to
"Login" or "Callback Login". "Login" or "Callback Login".
6.14.1. Login-IP-Host AVP 6.15.1. Login-IP-Host AVP
The Login-IP-Host AVP (AVP Code 14) [RADIUS] is of type OctetString The Login-IP-Host AVP (AVP Code 14) [RADIUS] is of type OctetString
and contains the IPv4 address of a host with which to connect the and contains the IPv4 address of a host with which to connect the
user when the Login-Service AVP is included. It MAY be used in an user when the Login-Service AVP is included. It MAY be used in an
AA-Request command as a hint to the Diameter Server that a specific AA-Request command as a hint to the Diameter Server that a specific
host is desired, but the Diameter Server is not required to honor the host is desired, but the Diameter Server is not required to honor the
hint in the AA-Answer. hint in the AA-Answer.
Two addresses have special significance: All ones and 0. The value Two addresses have special significance: All ones and 0. The value
of all ones indicates that the NAS SHOULD allow the user to select an of all ones indicates that the NAS SHOULD allow the user to select an
address. The value 0 indicates that the NAS SHOULD select a host to address. The value 0 indicates that the NAS SHOULD select a host to
connect the user to. connect the user to.
6.14.2. Login-IPv6-Host AVP 6.15.2. Login-IPv6-Host AVP
The Login-IPv6-Host AVP (AVP Code 98) [RADIUSIPv6] is of type The Login-IPv6-Host AVP (AVP Code 98) [RADIUSIPv6] is of type
OctetString and contains the IPv6 address of a host with which to OctetString and contains the IPv6 address of a host with which to
connect the user when the Login-Service AVP is included. It MAY be connect the user when the Login-Service AVP is included. It MAY be
used in an AA-Request command as a hint to the Diameter Server that a used in an AA-Request command as a hint to the Diameter Server that a
specific host is desired, but the Diameter Server is not required to specific host is desired, but the Diameter Server is not required to
honor the hint in the AA-Answer. honor the hint in the AA-Answer.
Two addresses have special significance: Two addresses have special significance:
0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF and 0. The value 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF and 0. The value
0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF indicates that the NAS SHOULD 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF indicates that the NAS SHOULD
allow the user to select an address. The value 0 indicates that the allow the user to select an address. The value 0 indicates that the
NAS SHOULD select a host to connect the user to. NAS SHOULD select a host to connect the user to.
6.14.3. Login-Service AVP 6.15.3. Login-Service AVP
The Login-Service AVP (AVP Code 15) is of type Enumerated and The Login-Service AVP (AVP Code 15) is of type Enumerated and
contains the service which should be used to connect the user to the contains the service which should be used to connect the user to the
login host. This AVP SHOULD only be present in authorization login host. This AVP SHOULD only be present in authorization
responses. responses.
The supported values are listed in [RADIUSTypes]. The following list The supported values are listed in [RADIUSTypes]. The following list
is informational: is informational:
0 Telnet 0 Telnet
1 Rlogin 1 Rlogin
2 TCP Clear 2 TCP Clear
3 PortMaster (proprietary) 3 PortMaster (proprietary)
4 LAT 4 LAT
5 X25-PAD 5 X25-PAD
6 X25-T3POS 6 X25-T3POS
8 TCP Clear Quiet (suppresses any NAS-generated connect 8 TCP Clear Quiet (suppresses any NAS-generated connect
string) string)
6.15. TCP Services 6.16. TCP Services
The AVPs described in this section MAY be present if the Login- The AVPs described in this section MAY be present if the Login-
Service AVP is set to Telnet, Rlogin, TCP Clear or TCP Clear Quiet. Service AVP is set to Telnet, Rlogin, TCP Clear or TCP Clear Quiet.
6.15.1. Login-TCP-Port AVP 6.16.1. Login-TCP-Port AVP
The Login-TCP-Port AVP (AVP Code 16) is of type Unsigned32 and The Login-TCP-Port AVP (AVP Code 16) is of type Unsigned32 and
contains the TCP port with which the user is to be connected, when contains the TCP port with which the user is to be connected, when
the Login-Service AVP is also present. This AVP SHOULD only be the Login-Service AVP is also present. This AVP SHOULD only be
present in authorization responses. The value MUST NOT be greater present in authorization responses. The value MUST NOT be greater
than 65535. than 65535.
6.16. LAT Services 6.17. LAT Services
The AVPs described in this section MAY be present if the Login- The AVPs described in this section MAY be present if the Login-
Service AVP is set to LAT [LAT]. Service AVP is set to LAT [LAT].
6.16.1. Login-LAT-Service AVP 6.17.1. Login-LAT-Service AVP
The Login-LAT-Service AVP (AVP Code 34) is of type OctetString and The Login-LAT-Service AVP (AVP Code 34) is of type OctetString and
contains the system with which the user is to be connected by LAT. It contains the system with which the user is to be connected by LAT. It
MAY be used in an authorization request as a hint to the server that MAY be used in an authorization request as a hint to the server that
a specific service is desired, but the server is not required to a specific service is desired, but the server is not required to
honor the hint in the corresponding response. This AVP MUST only be honor the hint in the corresponding response. This AVP MUST only be
present in the response if the Login-Service AVP states that LAT is present in the response if the Login-Service AVP states that LAT is
desired. desired.
Administrators use the service attribute when dealing with clustered Administrators use the service attribute when dealing with clustered
skipping to change at page 46, line 11 skipping to change at page 46, line 41
Alternately, some administrators want particular users to use certain Alternately, some administrators want particular users to use certain
machines as a primitive form of load balancing (although LAT knows machines as a primitive form of load balancing (although LAT knows
how to do load balancing itself). how to do load balancing itself).
The String field contains the identity of the LAT service to use. The String field contains the identity of the LAT service to use.
The LAT Architecture allows this string to contain $ (dollar), - The LAT Architecture allows this string to contain $ (dollar), -
(hyphen), . (period), _ (underscore), numerics, upper and lower case (hyphen), . (period), _ (underscore), numerics, upper and lower case
alphabetics, and the ISO Latin-1 character set extension [ISOLatin]. alphabetics, and the ISO Latin-1 character set extension [ISOLatin].
All LAT string comparisons are case insensitive. All LAT string comparisons are case insensitive.
6.16.2. Login-LAT-Node AVP 6.17.2. Login-LAT-Node AVP
The Login-LAT-Node AVP (AVP Code 35) is of type OctetString and The Login-LAT-Node AVP (AVP Code 35) is of type OctetString and
contains the Node with which the user is to be automatically contains the Node with which the user is to be automatically
connected by LAT. It MAY be used in an authorization request as a connected by LAT. It MAY be used in an authorization request as a
hint to the server that a specific LAT node is desired, but the hint to the server that a specific LAT node is desired, but the
server is not required to honor the hint in the corresponding server is not required to honor the hint in the corresponding
response. This AVP MUST only be present in a response if the Login- response. This AVP MUST only be present in a response if the Login-
Service-Type AVP is set to LAT. Service-Type AVP is set to LAT.
The String field contains the identity of the LAT service to use. The String field contains the identity of the LAT service to use.
The LAT Architecture allows this string to contain $ (dollar), - The LAT Architecture allows this string to contain $ (dollar), -
(hyphen), . (period), _ (underscore), numerics, upper and lower case (hyphen), . (period), _ (underscore), numerics, upper and lower case
alphabetics, and the ISO Latin-1 character set extension [ISOLatin]. alphabetics, and the ISO Latin-1 character set extension [ISOLatin].
All LAT string comparisons are case insensitive. All LAT string comparisons are case insensitive.
6.16.3. Login-LAT-Group AVP 6.17.3. Login-LAT-Group AVP
The Login-LAT-Group AVP (AVP Code 36) is of type OctetString and The Login-LAT-Group AVP (AVP Code 36) is of type OctetString and
contains a string identifying the LAT group codes which this user is contains a string identifying the LAT group codes which this user is
authorized to use. It MAY be used in an authorization request as a authorized to use. It MAY be used in an authorization request as a
hint to the server that a specific group is desired, but the server hint to the server that a specific group is desired, but the server
is not required to honor the hint in the corresponding response. This is not required to honor the hint in the corresponding response. This
AVP MUST only be present in a response if the Login-Service-Type AVP AVP MUST only be present in a response if the Login-Service-Type AVP
is set to LAT. is set to LAT.
LAT supports 256 different group codes, which LAT uses as a form of LAT supports 256 different group codes, which LAT uses as a form of
skipping to change at page 47, line 5 skipping to change at page 47, line 35
Administrators can assign one or more of the group code bits at the Administrators can assign one or more of the group code bits at the
LAT service provider; it will only accept LAT connections that have LAT service provider; it will only accept LAT connections that have
these group codes set in the bit map. The administrators assign a these group codes set in the bit map. The administrators assign a
bitmap of authorized group codes to each user; LAT gets these from bitmap of authorized group codes to each user; LAT gets these from
the operating system, and uses these in its requests to the service the operating system, and uses these in its requests to the service
providers. providers.
The codification of the range of allowed usage of this field is The codification of the range of allowed usage of this field is
outside the scope of this specification. outside the scope of this specification.
6.16.4. Login-LAT-Port AVP 6.17.4. Login-LAT-Port AVP
The Login-LAT-Port AVP (AVP Code 63) is of type OctetString and The Login-LAT-Port AVP (AVP Code 63) is of type OctetString and
contains the Port with which the user is to be connected by LAT. It contains the Port with which the user is to be connected by LAT. It
MAY be used in an authorization request as a hint to the server that MAY be used in an authorization request as a hint to the server that
a specific port is desired, but the server is not required to honor a specific port is desired, but the server is not required to honor
the hint in the corresponding response. This AVP MUST only be present the hint in the corresponding response. This AVP MUST only be present
in a response if the Login-Service-Type AVP is set to LAT. in a response if the Login-Service-Type AVP is set to LAT.
The String field contains the identity of the LAT service to use. The String field contains the identity of the LAT service to use.
The LAT Architecture allows this string to contain $ (dollar), - The LAT Architecture allows this string to contain $ (dollar), -
skipping to change at page 75, line 50 skipping to change at page 76, line 50
Framed-Compression | 0+ | 0+ | Framed-Compression | 0+ | 0+ |
Framed-Interface-Id | 0-1 | 0-1 | Framed-Interface-Id | 0-1 | 0-1 |
Framed-IP-Address | 0-1 | 0-1 | Framed-IP-Address | 0-1 | 0-1 |
Framed-IP-Netmask | 0-1 | 0-1 | Framed-IP-Netmask | 0-1 | 0-1 |
Framed-IPv6-Prefix | 0+ | 0+ | Framed-IPv6-Prefix | 0+ | 0+ |
Framed-IPv6-Pool | 0 | 0-1 | Framed-IPv6-Pool | 0 | 0-1 |
Framed-IPv6-Route | 0 | 0+ | Framed-IPv6-Route | 0 | 0+ |
Framed-IPX-Network | 0 | 0-1 | Framed-IPX-Network | 0 | 0-1 |
Framed-MTU | 0-1 | 0-1 | Framed-MTU | 0-1 | 0-1 |
Framed-Pool | 0 | 0-1 | Framed-Pool | 0 | 0-1 |
Framed-Protocol | 0-1 | 0-1 |
------------------------------|-----+-----+ ------------------------------|-----+-----+
+-----------+ +-----------+
| Command | | Command |
|-----+-----+ |-----+-----+
Attribute Name | AAR | AAA | Attribute Name | AAR | AAA |
------------------------------|-----+-----+ ------------------------------|-----+-----+
Framed-Protocol | 0-1 | 0-1 |
Framed-Route | 0 | 0+ | Framed-Route | 0 | 0+ |
Framed-Routing | 0 | 0-1 | Framed-Routing | 0 | 0-1 |
Idle-Timeout | 0 | 0-1 | Idle-Timeout | 0 | 0-1 |
Login-IP-Host | 0+ | 0+ | Login-IP-Host | 0+ | 0+ |
Login-IPv6-Host | 0+ | 0+ | Login-IPv6-Host | 0+ | 0+ |
Login-LAT-Group | 0-1 | 0-1 | Login-LAT-Group | 0-1 | 0-1 |
Login-LAT-Node | 0-1 | 0-1 | Login-LAT-Node | 0-1 | 0-1 |
Login-LAT-Port | 0-1 | 0-1 | Login-LAT-Port | 0-1 | 0-1 |
Login-LAT-Service | 0-1 | 0-1 | Login-LAT-Service | 0-1 | 0-1 |
Login-Service | 0 | 0-1 | Login-Service | 0 | 0-1 |
skipping to change at page 76, line 37 skipping to change at page 77, line 36
NAS-Port-Id | 0-1 | 0 | NAS-Port-Id | 0-1 | 0 |
NAS-Port-Type | 0-1 | 0 | NAS-Port-Type | 0-1 | 0 |
Origin-Host | 1 | 1 | Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 | Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 | Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 | Originating-Line-Info | 0-1 | 0 |
Password-Retry | 0 | 0-1 | Password-Retry | 0 | 0-1 |
Port-Limit | 0-1 | 0-1 | Port-Limit | 0-1 | 0-1 |
Prompt | 0 | 0-1 | Prompt | 0 | 0-1 |
Proxy-Info | 0+ | 0+ | Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0 | 0+ |
Re-Auth-Request-Type | 0 | 0-1 | Re-Auth-Request-Type | 0 | 0-1 |
Redirect-Host | 0 | 0+ | Redirect-Host | 0 | 0+ |
Redirect-Host-Usage | 0 | 0-1 | Redirect-Host-Usage | 0 | 0-1 |
Redirect-Max-Cache-Time | 0 | 0-1 | Redirect-Max-Cache-Time | 0 | 0-1 |
Reply-Message | 0 | 0+ | Reply-Message | 0 | 0+ |
Result-Code | 0 | 1 | Result-Code | 0 | 1 |
Route-Record | 0+ | 0+ | Route-Record | 0+ | 0+ |
Service-Type | 0-1 | 0-1 | Service-Type | 0-1 | 0-1 |
Session-Id | 1 | 1 | Session-Id | 1 | 1 |
Session-Timeout | 0 | 0-1 | Session-Timeout | 0 | 0-1 |
skipping to change at page 77, line 50 skipping to change at page 79, line 43
Acct-Tunnel-Packets-Lost | 0-1 | 0 | Acct-Tunnel-Packets-Lost | 0-1 | 0 |
Authorization-Lifetime | 0-1 | 0 | Authorization-Lifetime | 0-1 | 0 |
Callback-Id | 0-1 | 0 | Callback-Id | 0-1 | 0 |
Callback-Number | 0-1 | 0 | Callback-Number | 0-1 | 0 |
Called-Station-Id | 0-1 | 0 | Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 | Calling-Station-Id | 0-1 | 0 |
Class | 0+ | 0+ | Class | 0+ | 0+ |
Connection-Info | 0+ | 0 | Connection-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 | Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 | Destination-Realm | 1 | 0 |
Event-Timestamp | 0-1 | 0-1 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0 | 0+ |
---------------------------------------|-----+-----+ ---------------------------------------|-----+-----+
+-----------+ +-----------+
| Command | | Command |
|-----+-----+ |-----+-----+
Attribute Name | ACR | ACA | Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+ ---------------------------------------|-----+-----+
Event-Timestamp | 0-1 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Framed-AppleTalk-Link | 0-1 | 0 | Framed-AppleTalk-Link | 0-1 | 0 |
Framed-AppleTalk-Network | 0-1 | 0 | Framed-AppleTalk-Network | 0-1 | 0 |
Framed-AppleTalk-Zone | 0-1 | 0 | Framed-AppleTalk-Zone | 0-1 | 0 |
Framed-Compression | 0-1 | 0 | Framed-Compression | 0-1 | 0 |
Framed-IP-Address | 0-1 | 0 | Framed-IP-Address | 0-1 | 0 |
Framed-IP-Netmask | 0-1 | 0 | Framed-IP-Netmask | 0-1 | 0 |
Framed-IPv6-Prefix | 0+ | 0 | Framed-IPv6-Prefix | 0+ | 0 |
Framed-IPv6-Pool | 0-1 | 0 | Framed-IPv6-Pool | 0-1 | 0 |
Framed-IPX-Network | 0-1 | 0 | Framed-IPX-Network | 0-1 | 0 |
Framed-MTU | 0-1 | 0 | Framed-MTU | 0-1 | 0 |
Framed-Pool | 0-1 | 0 | Framed-Pool | 0-1 | 0 |
Framed-Protocol | 0-1 | 0 | Framed-Protocol | 0-1 | 0 |
Framed-Route | 0-1 | 0 | Framed-Route | 0-1 | 0 |
Framed-Routing | 0-1 | 0 | Framed-Routing | 0-1 | 0 |
NAS-Filter-Rule | 0-1 | 0 | NAS-Filter-Rule | 0+ | 0 |
NAS-Identifier | 0-1 | 0-1 | NAS-Identifier | 0-1 | 0-1 |
NAS-IP-Address | 0-1 | 0-1 | NAS-IP-Address | 0-1 | 0-1 |
NAS-IPv6-Address | 0-1 | 0-1 | NAS-IPv6-Address | 0-1 | 0-1 |
NAS-Port | 0-1 | 0-1 | NAS-Port | 0-1 | 0-1 |
NAS-Port-Id | 0-1 | 0-1 | NAS-Port-Id | 0-1 | 0-1 |
NAS-Port-Type | 0-1 | 0-1 | NAS-Port-Type | 0-1 | 0-1 |
Origin-Host | 1 | 1 | Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 | Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 | Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 | Originating-Line-Info | 0-1 | 0 |
Proxy-Info | 0+ | 0+ | Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0+ | 0 |
Route-Record | 0+ | 0+ | Route-Record | 0+ | 0+ |
Result-Code | 0 | 1 | Result-Code | 0 | 1 |
Service-Type | 0-1 | 0-1 | Service-Type | 0-1 | 0-1 |
Session-Id | 1 | 1 | Session-Id | 1 | 1 |
Termination-Cause | 0-1 | 0-1 | Termination-Cause | 0-1 | 0-1 |
Tunnel-Assignment-Id | 0-1 | 0 | Tunnel-Assignment-Id | 0-1 | 0 |
Tunnel-Client-Endpoint | 0-1 | 0 | Tunnel-Client-Endpoint | 0-1 | 0 |
Tunnel-Medium-Type | 0-1 | 0 | Tunnel-Medium-Type | 0-1 | 0 |
Tunnel-Private-Group-Id | 0-1 | 0 | Tunnel-Private-Group-Id | 0-1 | 0 |
Tunnel-Server-Endpoint | 0-1 | 0 | Tunnel-Server-Endpoint | 0-1 | 0 |
skipping to change at page 79, line 40 skipping to change at page 81, line 40
Authorization-Lifetime | 0-1 | 0 | Authorization-Lifetime | 0-1 | 0 |
Callback-Id | 0-1 | 0 | Callback-Id | 0-1 | 0 |
Callback-Number | 0-1 | 0 | Callback-Number | 0-1 | 0 |
Called-Station-Id | 0-1 | 0 | Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 | Calling-Station-Id | 0-1 | 0 |
Class | 0+ | 0+ | Class | 0+ | 0+ |
Connection-Info | 0+ | 0 | Connection-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 | Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 | Destination-Realm | 1 | 0 |
Event-Timestamp | 0-1 | 0-1 | Event-Timestamp | 0-1 | 0-1 |
Error-Reporting-Host | 0 | 0+ | Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0 | 0+ |
Login-IP-Host | 0+ | 0 | Login-IP-Host | 0+ | 0 |
Login-IPv6-Host | 0+ | 0 | Login-IPv6-Host | 0+ | 0 |
Login-LAT-Service | 0-1 | 0 | Login-LAT-Service | 0-1 | 0 |
Login-LAT-Node | 0-1 | 0 | Login-LAT-Node | 0-1 | 0 |
Login-LAT-Group | 0-1 | 0 | Login-LAT-Group | 0-1 | 0 |
Login-LAT-Port | 0-1 | 0 | Login-LAT-Port | 0-1 | 0 |
Login-Service | 0-1 | 0 | Login-Service | 0-1 | 0 |
Login-TCP-Port | 0-1 | 0 | Login-TCP-Port | 0-1 | 0 |
---------------------------------------|-----+-----+ ---------------------------------------|-----+-----+
+-----------+ +-----------+
skipping to change at page 80, line 20 skipping to change at page 82, line 20
NAS-IP-Address | 0-1 | 0-1 | NAS-IP-Address | 0-1 | 0-1 |
NAS-IPv6-Address | 0-1 | 0-1 | NAS-IPv6-Address | 0-1 | 0-1 |
NAS-Port | 0-1 | 0-1 | NAS-Port | 0-1 | 0-1 |
NAS-Port-Id | 0-1 | 0-1 | NAS-Port-Id | 0-1 | 0-1 |
NAS-Port-Type | 0-1 | 0-1 | NAS-Port-Type | 0-1 | 0-1 |
Origin-Host | 1 | 1 | Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 | Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 | Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 | Originating-Line-Info | 0-1 | 0 |
Proxy-Info | 0+ | 0+ | Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0+ | 0 |
Route-Record | 0+ | 0+ | Route-Record | 0+ | 0+ |
Result-Code | 0 | 1 | Result-Code | 0 | 1 |
Session-Id | 1 | 1 | Session-Id | 1 | 1 |
Service-Type | 0-1 | 0-1 | Service-Type | 0-1 | 0-1 |
Termination-Cause | 0-1 | 0-1 | Termination-Cause | 0-1 | 0-1 |
User-Name | 0-1 | 0-1 | User-Name | 0-1 | 0-1 |
Vendor-Specific-Application-Id | 0-1 | 0-1 | Vendor-Specific-Application-Id | 0-1 | 0-1 |
---------------------------------------|-----+-----+ ---------------------------------------|-----+-----+
11. IANA Considerations 11. IANA Considerations
This section provides guidance to the Internet Assigned Numbers This section provides guidance to the Internet Assigned Numbers
Authority (IANA) regarding registration of values related to the Authority (IANA) regarding registration of values related to the
Diameter protocol, in accordance with BCP 26 [IANAConsid]. Diameter protocol, in accordance with BCP 26 [IANAConsid].
This document defines values in the namespaces that have been created This document defines values in the namespaces that have been created
and defined in the Diameter Base [Base]. The IANA Considerations and defined in the Diameter Base [Base]. The IANA Considerations
section of that document details the assignment criteria. Values section of that document details the assignment criteria. Values
assigned in this document, or by future IANA action, must be assigned in this document, or by future IANA action, must be
coordinated within this shared namespace. coordinated within this shared namespace.
11.1. Command Codes 11.1. Command Codes
This specification assigns the values 265 and 268 from the Command This specification assigns the values 265 and 268 from the Command
Code namespace defined in [Base]. See sections 3.1 and 3.2 for the Code namespace defined in [Base]. See sections 3.1 and 3.2 for the
assignment of the namespace in this specification. assignment of the namespace in this specification.
11.2. AVP Codes 11.2. AVP Codes
This specification assigns the values 363-366 and 400-406 from the This specification assigns the values 363-366 and 400-407 from the
AVP Code namespace defined in [Base]. See sections 4, and 5 for the AVP Code namespace defined in [Base]. See sections 4, and 5 for the
assignment of the namespace in this specification. Note that the assignment of the namespace in this specification. Note that the
values 363-366 are jointly, but consistently, assigned in [DiamMIP]. values 363-366 are jointly, but consistently, assigned in [DiamMIP].
This document also creates one new namespace to be managed by IANA, This document also creates one new namespace to be managed by IANA,
as described in Section 11.5. as described in Section 11.5.
This specification also specifies the use of AVPs in the 0-255 range, This specification also specifies the use of AVPs in the 0-255 range,
which are defined in [RADIUSTypes]. These values are assigned by the which are defined in [RADIUSTypes]. These values are assigned by the
policy in RFC 2865 Section 6. [RADIUS] policy in RFC 2865 Section 6. [RADIUS]
skipping to change at page 84, line 38 skipping to change at page 86, line 38
[ARAP] Apple Remote Access Protocol (ARAP) Version 2.0 External [ARAP] Apple Remote Access Protocol (ARAP) Version 2.0 External
Reference Specification", Apple Computer, September 1994, Reference Specification", Apple Computer, September 1994,
R0612LL/B R0612LL/B
[IPX] Novell, Inc., "NetWare System Technical Interface [IPX] Novell, Inc., "NetWare System Technical Interface
Overview", June 1989, # 883-000780-001 Overview", June 1989, # 883-000780-001
[LAT] Local Area Transport (LAT) Specification V5.0, Digital [LAT] Local Area Transport (LAT) Specification V5.0, Digital
Equipment Corp., AA-NL26A-TE, June 1989 Equipment Corp., AA-NL26A-TE, June 1989
[DIFFSERV] Nichols, K., Blake, S., Baker, F. and D. Black,
"Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474, December
1998.
[DIFFSERVAF] Heinanen, J., Baker, F., Weiss, W. and J. Wroclawski,
"Assured Forwarding PHB Group", RFC 2597, June 1999.
[DIFFSERVEF] Davie, B., Charny, A., Bennet, J., Benson, K., Le Boudec,
J., Courtney, W., Davari, S., Firoiu, V. and D. Stiliadis,
"An Expedited Forwarding PHB", RFC 3246, March 2002.
[UTF-8] F. Yergeau, "UTF-8, a transformation format of ISO 10646", [UTF-8] F. Yergeau, "UTF-8, a transformation format of ISO 10646",
STD 63, RFC 3629, November 2003 STD 63, RFC 3629, November 2003
[ISOLatin] ISO 8859. International Standard -- Information Processing [ISOLatin] ISO 8859. International Standard -- Information Processing
-- 8-bit Single-Byte Coded Graphic Character Sets -- Part -- 8-bit Single-Byte Coded Graphic Character Sets -- Part
1: Latin Alphabet No. 1, ISO 8859-1:1987. URL: 1: Latin Alphabet No. 1, ISO 8859-1:1987. URL:
<http://www.iso.ch/cate/d16338.html> <http://www.iso.ch/cate/d16338.html>
[PPP] W. Simpson, Editor, "The Point-to-Point Protocol (PPP)", [PPP] W. Simpson, Editor, "The Point-to-Point Protocol (PPP)",
STD 51, RFC 1661, July 1994 STD 51, RFC 1661, July 1994
 End of changes. 87 change blocks. 
205 lines changed or deleted 308 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/