DHCPv6 Options for LWM2M bootstrap information
draft-ietf-dhc-dhcpv6-lwm2m-bootstrap-options-00
DHC working group S. Nalluri
Internet-Draft Ericsson
Intended status: Standards Track August 28, 2017
Expires: March 1, 2018
DHCPv6 Options for LWM2M bootstrap information
draft-ietf-dhc-dhcpv6-lwm2m-bootstrap-options-00
Abstract
This document defines Dynamic Host Configuration Protocol and Dynamic
Host Configuration Protocol version 6 (DHCPv6) Options for LWM2M
client bootstrap information, which are used to carry Uniform
Resource Locater of LWM2M bootstrap server and certificate that
validates the public key presented by server.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on March 1, 2018.
Copyright Notice
Copyright (c) 2017 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.
Nalluri Expires March 1, 2018 [Page 1]
Internet-Draft DHCPv6 Options for LWM2M August 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. LWM2M bootstrap server information through DHC . . . . . . . 3
3.1. DHCPv6 option for LWM2M bootstrap server URI . . . . . . 3
3.2. DHCPv6 option for LWM2M server certificate . . . . . . . 4
3.3. DHCPv4 option for LWM2M bootstrap server URI . . . . . . 4
3.4. DHCPv4 option for LWM2M server certificate . . . . . . . 5
4. LWM2M-server-certificate encoding . . . . . . . . . . . . . . 5
5. Appearance of Option . . . . . . . . . . . . . . . . . . . . 6
5.1. Appearance of options in DHCPv6 control messages . . . . 6
5.2. Appearance of options in DHCPv4 control messages . . . . 6
6. Configuration Guidelines for the Server . . . . . . . . . . . 7
7. DHCPv4/DHCPv6 Client Behavior . . . . . . . . . . . . . . . . 7
8. Relay agent Behavior . . . . . . . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 8
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 8
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
12.1. Normative References . . . . . . . . . . . . . . . . . . 9
12.2. Informative References . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
Light weight machine to machine (LWM2M) protocol is used to manage
end device life cycle in machine to machine communication scenarios.
LWM2M device bootstrap is an optional life cycle phase for devices to
get needed information when starting up for first time. Information
gathered during bootstrapping might include management server details
and security certificates required to establish connectivity with
management server. Information required to connect with bootstrap
server might be hard coded during device manufacturing phase.
Hard coding configuration by device manufacturer forces device
operator to use same configuration as hard coded. It is possible
that reachability information of bootstrap server that is hard coded
may be outdated and boot strap server reachability might fail during
first use of device. In such cases connectivity with bootstrap
server is possible only through device software upgrade.
2. Terminology
Show full document text