idnits 2.17.1 draft-calhoun-diameter-authent-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories -- however, there's a paragraph with a matching beginning. Boilerplate error? == The page length should not exceed 58 lines per page, but there was 54 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 55 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 21 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([4], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2439 has weird spacing: '... copied and ...' == Line 2440 has weird spacing: '...s, and deriv...' == Line 2441 has weird spacing: '...blished and...' == Line 2442 has weird spacing: '...ed, in whole...' == Line 2443 has weird spacing: '...hat the above...' == (5 more instances...) == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '11' is defined on line 2393, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 2398, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2138 (ref. '1') (Obsoleted by RFC 2865) == Outdated reference: A later version (-18) exists of draft-calhoun-diameter-08 -- Possible downref: Normative reference to a draft: ref. '2' ** Obsolete normative reference: RFC 2486 (ref. '3') (Obsoleted by RFC 4282) ** Downref: Normative reference to an Informational RFC: RFC 2477 (ref. '4') -- Possible downref: Normative reference to a draft: ref. '5' -- Possible downref: Non-RFC (?) normative reference: ref. '8' ** Obsolete normative reference: RFC 1717 (ref. '9') (Obsoleted by RFC 1990) == Outdated reference: A later version (-08) exists of draft-calhoun-diameter-res-mgmt-02 -- Possible downref: Normative reference to a draft: ref. '10' == Outdated reference: A later version (-09) exists of draft-calhoun-diameter-framework-02 -- Possible downref: Normative reference to a draft: ref. '11' == Outdated reference: A later version (-04) exists of draft-calhoun-diameter-proxy-02 -- Possible downref: Normative reference to a draft: ref. '13' Summary: 13 errors (**), 0 flaws (~~), 17 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET DRAFT Pat R. Calhoun 2 Category: Standards Track Sun Microsystems, Inc. 3 Title: draft-calhoun-diameter-authent-07.txt William Bulley 4 Date: October 1999 Merit Network, Inc. 6 DIAMETER 7 Dial-Up (ROAMOPS) Extensions 9 Status of this Memo 11 This document is an individual contribution for consideration by the 12 AAA Working Group of the Internet Engineering Task Force. Comments 13 should be submitted to the diameter@ipass.com mailing list. 15 Distribution of this memo is unlimited. 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC2026. Internet-Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its areas, 20 and its working groups. Note that other groups may also distribute 21 working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at: 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at: 34 http://www.ietf.org/shadow.html. 36 Abstract 38 This document describes the DIAMETER Dial-up User Authentication 39 Extension that is used for ROAMOPS [4] purposes. This specification 40 was carefully designed to ease the burden of servers that must act as 41 RADIUS/DIAMETER gateways, by re-using the same address space that 42 RADIUS has defined [1]. Further, by re-using the same address space, 43 it allows a single server to read the same dictiionary for both 44 DIAMETER and RADIUS. This backward compatibility will hopefully 45 facilitate deployment of DIAMETER. 47 Table of Contents 49 1.0 Introduction 50 1.1 Copyright Statement 51 1.2 Requirements language 52 1.3 Changes in version -06 53 1.4 Changes in version -07 54 2.0 Command Codes 55 2.1 AA-Request (AAR) 56 2.2 AA-Answer (AAA) 57 2.3 AA-Challenge-Ind (ACI) 58 3.0 DIAMETER AVPs 59 3.1 User-Name 60 3.2 User-Password 61 3.3 CHAP-Password 62 3.4 NAS-Port 63 3.5 Service-Type 64 3.6 Framed-Protocol 65 3.7 Framed-IP-Address 66 3.8 Framed-IP-Netmask 67 3.9 Framed-Routing 68 3.10 Filter-Id 69 3.11 Framed-MTU 70 3.12 Framed-Compression 71 3.13 Login-IP-Host 72 3.14 Login-Service 73 3.15 Login-TCP-Port 74 3.16 Reply-Message 75 3.17 Callback-Number 76 3.18 Callback-Id 77 3.19 Framed-Route 78 3.20 Framed-IPX-Network 79 3.21 Idle-Timeout 80 3.22 Called-Station-Id 81 3.23 Calling-Station-Id 82 3.24 Login-LAT-Service 83 3.25 Login-LAT-Node 84 3.26 Login-LAT-Group 85 3.27 Framed-AppleTalk-Link 86 3.28 Framed-AppleTalk-Network 87 3.29 Framed-AppleTalk-Zone 88 3.30 CHAP-Challenge 89 3.31 NAS-Port-Type 90 3.32 Port-Limit 91 3.33 Login-LAT-Port 92 3.34 Filter-Rule 93 3.35 Framed-Password-Policy 94 3.36 Table of Attributes 96 4.0 Protocol Definition 97 4.1 Feature Advertisement/Discovery 98 4.2 Authorization Procedure 99 4.3 Integration with Resource-Management 100 5.0 References 101 6.0 Acknowledgements 102 7.0 Authors' Addresses 103 8.0 Full Copyright Statement 105 1.0 Introduction 107 This document describes the DIAMETER Dial-up User Authentication 108 Extension that is used for ROAMOPS [4] purposes. This specification 109 was carefully designed to ease the burden of servers that must act as 110 RADIUS/DIAMETER gateways, by re-using the same address space that 111 RADIUS has defined [1]. Further, by re-using the same address space, 112 it allows a single server to read the same dictiionary for both 113 DIAMETER and RADIUS. This backward compatibility will hopefully 114 facilitate deployment of DIAMETER. 116 The Extension number for this draft is one (1). This value is used in 117 the Extension-Id AVP as defined in [2]. 119 1.1 Copyright Statement 121 Copyright (C) The Internet Society 1999. All Rights Reserved. 123 1.2 Requirements language 125 In this document, the key words "MAY", "MUST, "MUST NOT", "optional", 126 "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as 127 described in [12]. 129 1.3 Changes in version -06 131 The following changes have been made to version 06: 133 - Changes to AVP Header Flags 135 - Change to the document title 137 - Changed the Command-Specific AVP Flags in all command codes 138 defined. 140 - Added a reference to RFC 1994 (CHAP) 142 1.4 Changes in version -07 144 The following changes have been made to version 07: 146 - Changed the Filter-Rule Command Code AVP from 280 to 300 148 - Changed the Framed-Password-Policy Command Code AVP from 280 to 149 301 151 2.0 Command Codes 153 This document defines the following DIAMETER Commands. All DIAMETER 154 implementations supporting this extension MUST support all of the 155 following commands: 157 Command Name Command Code 158 ----------------------------------- 159 AA-Request 263 160 AA-Answer 264 161 AA-Challenge-Ind 265 163 2.1 AA-Request (AAR) 165 Description 167 The AA-Request message is used in order to request authentication 168 and authorization for a given user. 170 If Authentication is requested the User-Name attribute MUST be 171 present. If only Authorization is required it is possible to 172 authorize based on DNIS and ANI instead. However, it is not 173 possible to authenticate using a User-Name AVP and later 174 requesting authorization based on DNIS using the same Session-Id 175 (although the inverse is legal). 177 Note that the flag field MAY be used in this command in order to 178 indicate that either Authentication-Only or Authorization-Only is 179 required for the request. If the Authentication-Only bit is set 180 the response MUST NOT include any authorization information. Both 181 the Authenticate and Authorize bits MUST NOT be set at the same 182 time. To ensure that a user is both authenticated and authorized, 183 neither flag is set. 185 The AA-Request message MUST include a unique Session-Id AVP. If 186 The AA-Request is a result of a successful AA-Challenge-Ind the 187 Session-Id MUST be identical to the one provided in the initial 188 AA-Request. 190 Message Format 192 Section 3.36 contains a complete list of all valid AVPs for this 193 message. 195 ::= 196 197 198 199 [] 200 [] 201 [] 202 [] 203 { || 204 206 207 208 { || 209 ::= 306 307 308 309 [] 310 311 [] 312 [] 313 [] 314 [] 315 [] 316 317 318 319 { || 320 413 414 415 416 [] 417 418 [] 419 [] 420 [] 421 [] 422 423 424 425 { || 426 2388 [9] Sklower, Lloyd, McGregor, Carr, "The PPP Multilink Protocol 2389 (MP)", RFC 1717, November 1994. 2390 [10] Calhoun, Greene, "DIAMETER Resource Management Extension", 2391 draft-calhoun-diameter-res-mgmt-02.txt, Work in Progress, 2392 February 1999. 2393 [11] Calhoun, Zorn, Pan, "DIAMETER Framework", 2394 draft-calhoun-diameter-framework-02.txt, Work in Progress, 2395 December 1998. 2396 [12] S. Bradner, "Key words for use in RFCs to Indicate 2397 Requirement Levels", BCP 14, RFC 2119, March 1997. 2398 [13] P. Calhoun, W. Bulley, "DIAMETER Proxy Server Extensions", 2399 draft-calhoun-diameter-proxy-02.txt, Work in Progress, 2400 August 1999. 2402 6.0 Acknowledgements 2404 The Author wishes to thank Carl Rigney since much of the text in the 2405 document was shamefully copied from [1] as well as the following 2406 people for their help in the development of this protocol: 2408 Nancy Greene, Ryan Moats 2410 7.0 Authors' Addresses 2412 Questions about this memo can be directed to: 2414 Pat R. Calhoun 2415 Network and Security Research Center, Sun Labs 2416 Sun Microsystems, Inc. 2417 15 Network Circle 2418 Menlo Park, California, 94025 2419 USA 2421 Phone: 1-650-786-7733 2422 Fax: 1-650-786-6445 2423 E-mail: pcalhoun@eng.sun.com 2425 William Bulley 2426 Merit Network, Inc. 2427 4251 Plymouth Road, Suite C 2428 Ann Arbor, Michigan, 48105-2785 2429 USA 2431 Phone: 1-734-764-9993 2432 Fax: 1-734-647-3185 2433 E-mail: web@merit.edu 2435 8.0 Full Copyright Statement 2437 Copyright (C) The Internet Society (1999). All Rights Reserved. 2439 This document and translations of it may be copied and furnished to 2440 others, and derivative works that comment on or otherwise explain it 2441 or assist in its implmentation may be prepared, copied, published and 2442 distributed, in whole or in part, without restriction of any kind, 2443 provided that the above copyright notice and this paragraph are 2444 included on all such copies and derivative works. However, this docu- 2445 ment itself may not be modified in any way, such as by removing the 2446 copyright notice or references to the Internet Society or other Inter- 2447 net organizations, except as needed for the purpose of developing 2448 Internet standards in which case the procedures for copyrights defined 2449 in the Internet Standards process must be followed, or as required to 2450 translate it into languages other than English. The limited permis- 2451 sions granted above are perpetual and will not be revoked by the 2452 Internet Society or its successors or assigns. This document and the 2453 information contained herein is provided on an "AS IS" basis and THE 2454 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL 2455 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WAR- 2456 RANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY 2457 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 2458 PARTICULAR PURPOSE."