INTERNET-DRAFT                                         Krzysztof Grochla
Intended Status: <draft>                                    (Proximetry)
Expires: February 26, 28, 2011                                August 25 27 2010

                   IEEE 802.11 parameters DHCP Option
                     draft-ietf-dhc-80211-option-00
                     draft-ietf-dhc-80211-option-01

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that other
   groups may also distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html. This Internet-Draft will expire on
   February 26, 2011.

Copyright and License Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Abstract

   The wireless access points and other devices requires configuration
   of parameters such as channel, ESSID. This document describes the
   DHCP options to be used to configure these parameters.

Table of Contents

   1  Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 4
      1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
   2  IEEE 802.11 radio configuration DCHP option  . . . . . . . . . . 4 5
   3  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . . 5 6
   4. Security consideration . . . . . . . . . . . . . . . . . . . . . 5 6
   5. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . . 5 6
   6. Authors  . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
   7. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
      7.1. 6
      6.1. Normative References  . . . . . . . . . . . . . . . . . . . 5 6
   Author's Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6

1  Introduction

   The IEEE 802.11 networks are very popular for providing Internet
   access. The IP address of wireless network access points are
   typically configured using DHCP protocol, but require manual
   configuration of radio parameters. There exists also a few
   autoconfiguration schemas for wireless mesh networks relaying on DHCP
   protocol to configure the 802.11 interfaces. The additional options
   proposed in this document allow to use DHCP to provide the radio
   parameters in addition to the IP address, allowing to enable the
   autoconfiguration procedure. This option may be also used for easy
   manual configuration of basic parameters of wireless access points in
   one central point and distributing it by DHCP protocol.

1.1  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

2  IEEE 802.11 radio configuration DCHP option

   This section defines the DHCP option that configures the SSID and the
   channel number of IEEE 802.11 network. The options have the same
   structure for both DHCPv4 and DHCPv6. The option to set the number
   and the SSID has the format shown
   on the following figure:

   0                   1                   2                   3
   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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       option-code             |       option-length           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    channel    |  SSID length  |           SSID                               |
   +---------------+---------------+                               +
   |                                                               |
   +                                                               +
   |                          SSID                                 |
   +                          AC IPv6 Address                                                               +
   |                                                               |
   +                                                               +
   |                                                               |
   +                                                               +
   |                                                               |
   +                                                               +
   |                                                               |
   +                                                               +
   |                                                               |
   +                               +-------------------------------|
   |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   option-code: OPTION_80211_CHANN_SSID (TBD)

   option-length: Length of the option in octet, must be multiple of
   sixteen (16).

   A DHCP client while requesting the parameters for a IEEE 802.11
   interface that supports this option MAY request the 80211 Channel and
   SSID option.

   The DHCP server returns the option to the client if the server policy
   is configured to do so. The SSID and channel may be preconfigured or
   selected by any algorithm implemented on the server side. If the
   option is received the interface SHOULD be configured to SSID and
   channel transmitted, as long as they are valid for the device.

3  IANA Considerations

   The following DHCP option code for channel and SSID assignment must
   be assigned by IANA:

   Option Name                Value       Described in------------------
   --------------------------------- in
   ---------------------------------------------------
   OPTION_80211_CHANN_SSID    TBD         Section 2

4. Security consideration The security considerations in [RFC2131],
   [RFC2132] and [RFC3315] apply.  If an adversary manages to modify the
   response from a DHCP server or insert its own response, the interface
   may be configured to a SSID and channel provided by the intruder. In
   security sensitive environment this should be taken into
   consideration by network administrator.

5. Acknowledgments The following individuals are acknowledged for their
   contributions to this protocol specification: Walter Buga

6. Authors Krzysztof Grochla Proximetry Poland, Al. Rozdzienskiego 91
   40-203 Katowice, Poland

7. References

7.1.

6.1. Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
      Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2131]  Droms, R., "Dynamic Host Configuration Protocol",
    RFC 2131, March 1997.

   [RFC2132]  Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
   Extensions", RFC 2132, March 1997

Author's Addresses

   Krzysztof Grochla,
   Proximetry Poland,
   Al. Rozdzienskiego 91
   40-203 Katowice, Poland

   EMail: kgrochla@proximetry.com