idnits 2.17.1 draft-ietf-dhc-paa-option-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 20. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 316. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 327. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 334. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 340. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- 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.) -- The document date (December 18, 2006) is 6329 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-18) exists of draft-ietf-pana-pana-13 ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DHC Working Group L. Morand 3 Internet-Draft France Telecom R&D 4 Intended status: Standards Track A. Yegin 5 Expires: June 21, 2007 Samsung 6 S. Kumar 7 Tech Mahindra Ltd 8 S. Madanapalli 9 Samsung 10 December 18, 2006 12 DHCP options for PANA Authentication Agents 13 draft-ietf-dhc-paa-option-05 15 Status of this Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on June 21, 2007. 40 Copyright Notice 42 Copyright (C) The IETF Trust (2006). 44 Abstract 46 This document defines new DHCPv4 and DHCPv6 options that contain a 47 list of IP addresses to locate one or more of PANA Authentication 48 Agents (PAA). This is one of the methods that a PANA Client (PaC) 49 can use to locate PANA Authentication Agents (PAA). 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Specification of Requirements . . . . . . . . . . . . . . . . . 3 55 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 4. PANA Authentication Agent DHCPv4 Option . . . . . . . . . . . . 4 57 5. PANA Authentication Agent DHCPv6 Option . . . . . . . . . . . . 5 58 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 59 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 60 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 61 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 62 9.1. Normative References . . . . . . . . . . . . . . . . . . . 7 63 9.2. Informative References . . . . . . . . . . . . . . . . . . 7 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 65 Intellectual Property and Copyright Statements . . . . . . . . . . 9 67 1. Introduction 69 The Protocol for carrying Authentication for Network Access (PANA) 70 [I-D.ietf-pana-pana] defines a new Extensible Authentication Protocol 71 (EAP) [RFC3748] lower layer that uses IP between the protocol end- 72 points. 74 The PANA protocol is run between a PANA Client (PaC) and a PANA 75 Authentication Agent (PAA) in order to perform authentication and 76 authorization for the network access service. 78 This document specifies DHCPv4 [RFC2131] and DHCPv6 [RFC3315] options 79 that allow PANA client (PaC) to discover PANA Authentication Agents 80 (PAA). This is one of the methods for locating PAAs. 82 The DHCP options defined in this document are used only as a PAA 83 discovery mechanism. These DHCP options MUST NOT be used to perform 84 any negotiation on the use of PANA between the PaC and a PAA. 86 2. Specification of Requirements 88 In this document, several words are used to signify the requirements 89 of the specification. These words are often capitalized. The key 90 words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 91 "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document 92 are to be interpreted as described in [RFC2119]. 94 3. Terminology 96 This document uses the DHCP terminology defined in [RFC2131], 97 [RFC2132] and [RFC3315]. 99 This document uses the PANA terminology defined in 100 [I-D.ietf-pana-pana]. In particular, the following terms are 101 defined: 103 PANA Client (PaC): 105 The client side of the protocol that resides in the access 106 device (e.g., laptop, PDA, etc.). It is responsible for 107 providing the credentials in order to prove its identity 108 (authentication) for network access authorization. 110 PANA Authentication Agent (PAA): 112 The protocol entity in the access network whose responsibility 113 is to verify the credentials provided by a PANA client (PaC) 114 and authorize network access to the device associated with the 115 client and identified by a Device Identifier (DI). 117 4. PANA Authentication Agent DHCPv4 Option 119 This section defines a DHCPv4 option that carries a list of 32-bit 120 (binary) IPv4 addresses indicating one or more PANA Authentication 121 Agents (PAA) available to the PANA client. 123 The DHCPv4 option for PANA Authentication Agent has the format shown 124 in Fig. 1. 126 0 1 127 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 | option-code | option-length | 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 | | 132 + PAA IPv4 Address + 133 | | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 | ... | 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 Figure 1: PAA DHCPv4 option 139 option-code: OPTION_PANA_AGENT (TBD) 141 option-length: Length of the 'options' field in octets; 142 MUST be a multiple of four (4) 144 PAA IPv4 Address: IPv4 address of a PAA for the client to use. 145 The PAAs are listed in the order of preference 146 for use by the client. 148 A PaC (DHCPv4 client) SHOULD request the PAA DHCPv4 Option in a 149 Parameter Request List as described in [RFC2131] and [RFC2132]. 151 If configured with a (list of) PAA address(es), a DHCPv4 server 152 SHOULD send a client with the PAA DHCPv4 option, even if this option 153 is not explicitly requested by the client. 155 A PaC (DHCPv4 client) receiving the PAA DHCPv4 option SHOULD use the 156 (list of) IP address(es) to locate PAA. 158 The PaC (DHCPv4 client) MUST try the records in the order listed in 159 the PAA DHCPv4 option received from the DHCPv4 server. 161 5. PANA Authentication Agent DHCPv6 Option 163 This section defines a DHCPv6 option that carries a list of 128-bit 164 (binary) IPv6 addresses indicating one or more PANA Authentication 165 Agents (PAA) available to the PANA client. 167 The DHCPv6 option for PANA Authentication Agent has the format shown 168 in Fig. 2. 170 0 1 2 3 171 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | option-code | option-length | 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 | | 176 + + 177 | | 178 + PAA IPv6 Address + 179 | | 180 + + 181 | | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | .... | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 Figure 2: PAA DHCPv6 option 187 option-code: OPTION_PANA_AGENT (TBD) 189 option-length: Length of the 'options' field in octets; 190 MUST be a multiple of sixteen (16) 192 PAA IPv6 Address: IPv6 address of a PAA for the client to use. 193 The PAAs are listed in the order of preference 194 for use by the client. 196 A PaC DHCPv6 client SHOULD request the PAA DHCPv6 option in an 197 Options Request Option (ORO) as described in the DHCPv6 specification 198 [RFC3315]. 200 If configured with a (list of) PAA address(es), a DHCPv6 server 201 SHOULD send a client with the PAA DHCPv6 option, even if this option 202 is not explicitly requested by the client. 204 A PaC (DHCPv6 client) receiving the PAA DHCPv6 option SHOULD use the 205 (list of) IP address(es) to locate PAA. 207 The PaC (DHCPv6 client) MUST try the records in the order listed in 208 the PAA DHCPv6 option received from the DHCPv6 server. 210 6. IANA Considerations 212 The following DHCPv4 option code for PANA Authentication Agent option 213 MUST be assigned by IANA: 215 Option Name Value Described in 216 ----------------------------------------------- 217 OPTION_PANA_AGENT TBD Section 4 219 The following DHCPv6 option code for PANA Authentication Agent 220 options MUST be assigned by IANA: 222 Option Name Value Described in 223 ------------------------------------------------ 224 OPTION_PAA_AGENT TBD Section 5 226 7. Security Considerations 228 The security considerations in [RFC2131], [RFC2132] and [RFC3315] 229 apply. If an adversary manages to modify the response from a DHCP 230 server or insert its own response, a PANA Client could be led to 231 contact a rogue PANA Authentication Agent, possibly one that then 232 intercepts call requests or denies service. 234 In most of the networks, the DHCP exchange that delivers the options 235 prior to network access authentication is neither integrity protected 236 nor origin authenticated. Therefore, the options defined in this 237 document MUST NOT be used to perform any negotiation on the use of 238 PANA between the PANA Client and a PANA Authentication Agent. Using 239 the presence (or absence) of these DHCP options as an indication of 240 network mandating PANA authentication (or not) is an example such a 241 negotiation mechanism. This negotiation would allow bidding down 242 attacks by making the clients choose to use a lower-grade security 243 mechanism (or even no security at all). 245 8. Acknowledgements 247 We would like to thank to Ralph Droms, Stig Venaas, Ted Lemon, Andre 248 Kostur and Bernie Volz for their valuable comments. We would like to 249 thank also Jari Arkko, Thomas Norten, Bernard Aboba that provided 250 several draft reviews, as well as all members of the PANA and DHC 251 working groups that contribute to improve this document. 253 9. References 255 9.1. Normative References 257 [I-D.ietf-pana-pana] 258 Forsberg, D., "Protocol for Carrying Authentication for 259 Network Access (PANA)", draft-ietf-pana-pana-13 (work in 260 progress), December 2006. 262 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 263 Requirement Levels", BCP 14, RFC 2119, March 1997. 265 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", 266 RFC 2131, March 1997. 268 [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor 269 Extensions", RFC 2132, March 1997. 271 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 272 and M. Carney, "Dynamic Host Configuration Protocol for 273 IPv6 (DHCPv6)", RFC 3315, July 2003. 275 9.2. Informative References 277 [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. 278 Levkowetz, "Extensible Authentication Protocol (EAP)", 279 RFC 3748, June 2004. 281 Authors' Addresses 283 Lionel Morand 284 France Telecom R&D 286 Email: lionel.morand@orange-ft.com 287 Alper E. Yegin 288 Samsung 290 Email: alper01.yegin@partner.samsung.com 292 Suraj Kumar 293 Tech Mahindra Ltd 295 Email: surajk@techmahindra.com 297 Syam Madanapalli 298 Samsung 300 Email: syam@samsung.com 302 Full Copyright Statement 304 Copyright (C) The IETF Trust (2006). 306 This document is subject to the rights, licenses and restrictions 307 contained in BCP 78, and except as set forth therein, the authors 308 retain all their rights. 310 This document and the information contained herein are provided on an 311 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 312 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 313 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 314 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 315 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 316 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 318 Intellectual Property 320 The IETF takes no position regarding the validity or scope of any 321 Intellectual Property Rights or other rights that might be claimed to 322 pertain to the implementation or use of the technology described in 323 this document or the extent to which any license under such rights 324 might or might not be available; nor does it represent that it has 325 made any independent effort to identify any such rights. Information 326 on the procedures with respect to rights in RFC documents can be 327 found in BCP 78 and BCP 79. 329 Copies of IPR disclosures made to the IETF Secretariat and any 330 assurances of licenses to be made available, or the result of an 331 attempt made to obtain a general license or permission for the use of 332 such proprietary rights by implementers or users of this 333 specification can be obtained from the IETF on-line IPR repository at 334 http://www.ietf.org/ipr. 336 The IETF invites any interested party to bring to its attention any 337 copyrights, patents or patent applications, or other proprietary 338 rights that may cover technology that may be required to implement 339 this standard. Please address the information to the IETF at 340 ietf-ipr@ietf.org. 342 Acknowledgment 344 Funding for the RFC Editor function is provided by the IETF 345 Administrative Support Activity (IASA).