idnits 2.17.1 draft-grochla-80211-dhcp-option-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 and authors Copyright Line does not match the current year == Unrecognized Status in 'Intended Status: ', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- 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) == Missing Reference: 'RFC3315' is mentioned on line 139, but not defined ** Obsolete undefined reference: RFC 3315 (Obsoleted by RFC 8415) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Krzysztof Grochla 3 Intended Status: (Proximetry) 4 Expires: March 2, 2011 August 29 2010 6 IEEE 802.11 parameters DHCP Option 7 draft-grochla-80211-dhcp-option-00 9 Status of this Memo 11 This Internet-Draft is submitted to IETF in full conformance with the 12 provisions of BCP 78 and BCP 79. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that other 16 groups may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt. 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. This Internet-Draft will expire on 28 February 26, 2011. 30 Copyright and License Notice 32 Copyright (c) 2010 IETF Trust and the persons identified as the 33 document authors. All rights reserved. 35 This document is subject to BCP 78 and the IETF Trust's Legal 36 Provisions Relating to IETF Documents 37 (http://trustee.ietf.org/license-info) in effect on the date of 38 publication of this document. Please review these documents 39 carefully, as they describe your rights and restrictions with respect 40 to this document. Code Components extracted from this document must 41 include Simplified BSD License text as described in Section 4.e of 42 the Trust Legal Provisions and are provided without warranty as 43 described in the Simplified BSD License. 45 Abstract 47 The wireless access points and other devices requires configuration 48 of parameters such as channel, ESSID. This document describes the 49 DHCP options to be used to configure these parameters. 51 Table of Contents 53 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2 IEEE 802.11 radio configuration DCHP option . . . . . . . . . . 4 56 3 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 57 4. Security consideration . . . . . . . . . . . . . . . . . . . . . 5 58 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 59 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 60 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 61 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 63 1 Introduction 65 The IEEE 802.11 networks are very popular for providing Internet 66 access. The IP address of wireless network access points are 67 typically configured using DHCP protocol, but require manual 68 configuration of radio parameters. There exists also a few 69 autoconfiguration schemas for wireless mesh networks relaying on DHCP 70 protocol to configure the 802.11 interfaces. The additional options 71 proposed in this document allow to use DHCP to provide the radio 72 parameters in addition to the IP address, allowing to enable the 73 autoconfiguration procedure. This option may be also used for easy 74 manual configuration of basic parameters of wireless access points in 75 one central point and distributing it by DHCP protocol. 77 1.1 Terminology 79 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 80 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 81 document are to be interpreted as described in RFC 2119 [RFC2119]. 83 2 IEEE 802.11 radio configuration DCHP option 85 This section defines the DHCP option that configures the SSID and the 86 channel number of IEEE 802.11 network. The options have the same 87 structure for both DHCPv4 and DHCPv6. The option has the format shown 88 on the following figure: 90 0 1 2 3 91 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 92 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 93 | option-code | option-length | 94 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 95 | channel | SSID length | | 96 +---------------+---------------+ + 97 | | 98 + + 99 | SSID | 100 + + 101 | | 102 + + 103 | | 104 + + 105 | | 106 + + 107 | | 108 + + 109 | | 110 + +-------------------------------| 111 | | 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 option-code: OPTION_80211_CHANN_SSID (TBD) 116 option-length: Length of the option in octet, must be multiple of 117 sixteen (16). 119 A DHCP client while requesting the parameters for a IEEE 802.11 120 interface that supports this option MAY request the 80211 Channel and 121 SSID option. 123 The DHCP server returns the option to the client if the server policy 124 is configured to do so. The SSID and channel may be preconfigured or 125 selected by any algorithm implemented on the server side. If the 126 option is received the interface SHOULD be configured to SSID and 127 channel transmitted, as long as they are valid for the device. 129 3 IANA Considerations 131 The following DHCP option code for channel and SSID assignment must 132 be assigned by IANA: 134 Option Name Value Described in 135 --------------------------------------------------- 136 OPTION_80211_CHANN_SSID TBD Section 2 138 4. Security consideration The security considerations in [RFC2131], 139 [RFC2132] and [RFC3315] apply. If an adversary manages to modify the 140 response from a DHCP server or insert its own response, the interface 141 may be configured to a SSID and channel provided by the intruder. In 142 security sensitive environment this should be taken into 143 consideration by network administrator. 145 5. Acknowledgments The following individuals are acknowledged for their 146 contributions to this protocol specification: Walter Buga 148 6. References 150 6.1. Normative References 152 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 153 Requirement Levels", BCP 14, RFC 2119, March 1997. 155 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 156 2131, March 1997. 158 [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor 159 Extensions", RFC 2132, March 1997 161 Author's Addresses 163 Krzysztof Grochla, 164 Proximetry Poland, 165 Al. Rozdzienskiego 91 166 40-203 Katowice, Poland 168 EMail: kgrochla@proximetry.com