Re: [dhcwg] DHCP and DHCPv6 options for LWM2M services

Ted Lemon <> Mon, 09 January 2017 14:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 43308129CF0 for <>; Mon, 9 Jan 2017 06:21:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PUk_SxUERa0I for <>; Mon, 9 Jan 2017 06:21:06 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8DA97129503 for <>; Mon, 9 Jan 2017 06:21:06 -0800 (PST)
Received: by with SMTP id u25so525853723qki.2 for <>; Mon, 09 Jan 2017 06:21:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=2dEtkvkJhYzbMOMwhiBu8iiQRz85UPYIi9XxVwquw0A=; b=1ihdOrAHr5eV3vzQ5kcwTgTc6VgPgMqt9Z/MByasi3DiuuKc4DhZoen4wpSMtj8MpS ORLQism3h6Zz8zHvOhYc+tD7PpBs7uxFJoZj4HwLcBDgR1DQd7sKdcAcR6Ih9XVgUiox SmY+gQlX1NpsrY8H0PKlCdx+lV9XZ0PWNB8x+S4Q3Aens3coMsGXJwiP/r0gzbkv5qrc hDF3rIqeorImVvJ6P9+B3aynX17JTncDXqReQCUoHT36VJlogOoJ9B04x6DUrgRTvJC7 /hF0kWwT2KvSvIhfZVo2BUbB5MXnfnYjaZufoWi33xFFwbPb32NWElKau+EQhbUZyRMp 5Clg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=2dEtkvkJhYzbMOMwhiBu8iiQRz85UPYIi9XxVwquw0A=; b=Ce2xkl+nrf3NG8axtjPnD2Okkg2daGokajpY+ogsIF9sM6T+oru9mh+g0Bzl220Wmu i9Px37GlsKBBOgS5zYqGHdfPDS7sa4iUzKgSoeTJ+aqlDnX0KN2Uno6vqP8EUcgXRqy1 Heo0CFpuHUmq1jKEHTUSDTq/+afLMdWmCCl0S7lIbOd3l+4Tk5kv3l+N61FGfdTqoxAz 26vkrcQeEaRIzeuCN9v/TeyNdVbgGMdogczIhx8lZkawKs++ic6PCW81ke3sQ2T8hHEY EK6L6H/qLdvYN0q5NWz+4Rfxmgr2iDh/9QFzsvsEtyo6VPveKnIIPr9debSsQkSYTdx4 ZAZQ==
X-Gm-Message-State: AIkVDXK1Ubt+F5FS+QWONhyIGfWKBEaHOlcekSu6sFu5+aJaKp098yfZ91hk4lPafjsYLA==
X-Received: by with SMTP id b205mr78312566qkc.142.1483971665682; Mon, 09 Jan 2017 06:21:05 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id q3sm57437385qte.41.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Jan 2017 06:21:04 -0800 (PST)
From: Ted Lemon <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_07D78126-7453-43CF-A1C4-C0F3958A5C5E"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Mon, 9 Jan 2017 09:21:02 -0500
In-Reply-To: <>
To: Srinivasa Rao Nalluri <>
References: <>
X-Mailer: Apple Mail (2.3259)
Archived-At: <>
Cc: Amit Gupta X <>, "" <>, =?utf-8?Q?Ari_Ker=C3=A4nen?= <>, =?utf-8?Q?Jaime_Jim=C3=A9nez?= <>, Jan Melen <>
Subject: Re: [dhcwg] DHCP and DHCPv6 options for LWM2M services
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 09 Jan 2017 14:21:08 -0000

How would this be validated?

> On Jan 9, 2017, at 2:00 AM, Srinivasa Rao Nalluri <> wrote:
> Hi,
> Considering growing popularity of Internet of Things and relevant protocols like LWM2M/CoAP/MQTT, we in Ericsson see need for new DHCP options to make LWM2M service deployment easy and flexible.
> 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.
> So, we see need to introduce two options to support LWM2M server URL and LWM2M server certificate that validates public key provided by LWM2M server. Thus bootstrap related information can be gathered by LWM2M client during DHCP/DHCPv6 negotiation phase. Draft available at below link describes details. 
> <>
> This draft considers options for both DHCP and DHCPv6.
> I would like this draft to be considered by DHC working group as work item. Please contact me for any further details.
> With Regards
> Srinivasa Rao Nalluri
> Ericssion 
> India
> _______________________________________________
> dhcwg mailing list
> <>
> <>