IETF Logo Mail Archive

[dhcwg] DHCP and DHCPv6 options for LWM2M services

Srinivasa Rao Nalluri <srinivasa.rao.nalluri@ericsson.com> Mon, 09 January 2017 07:00 UTC

Return-Path: <srinivasa.rao.nalluri@ericsson.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5260129B35 for <dhcwg@ietfa.amsl.com>; Sun, 8 Jan 2017 23:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDg9vKxriEHw for <dhcwg@ietfa.amsl.com>; Sun, 8 Jan 2017 23:00:08 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9DCD12940C for <dhcwg@ietf.org>; Sun, 8 Jan 2017 23:00:07 -0800 (PST)
X-AuditID: c1b4fb25-00bff700000042ea-a4-587334f41fa9
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by (Symantec Mail Security) with SMTP id 5D.62.17130.4F433785; Mon, 9 Jan 2017 08:00:06 +0100 (CET)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.69) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 9 Jan 2017 08:00:04 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ZbF6beKftyX6boYKkQVtSLtm11FYlVeRmVFlgpE3mAk=; b=Ecd8U77vayYDTzQgnBKq6ecALBzd/27BPKrZdlTh+//6+wjzQuJciQm5ckoIf0UorH4ffiJts++kVeGx58pXJTI/egfJYx0xJPpkVqcVnyIxKuqocVJ5wv7aJU3CMpS3NE7LKgEqwY1o19R6ngsTXE3kYaPcYIOw00SFFgQ8eTQ=
Received: from HE1PR0701MB1914.eurprd07.prod.outlook.com (10.167.189.18) by HE1PR0701MB1914.eurprd07.prod.outlook.com (10.167.189.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.829.3; Mon, 9 Jan 2017 07:00:01 +0000
Received: from HE1PR0701MB1914.eurprd07.prod.outlook.com ([10.167.189.18]) by HE1PR0701MB1914.eurprd07.prod.outlook.com ([10.167.189.18]) with mapi id 15.01.0829.013; Mon, 9 Jan 2017 07:00:00 +0000
From: Srinivasa Rao Nalluri <srinivasa.rao.nalluri@ericsson.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHCP and DHCPv6 options for LWM2M services
Thread-Index: AdJqRXTE4zv4sumCQiCdFGjUYw4CPA==
Date: Mon, 09 Jan 2017 07:00:00 +0000
Message-ID: <HE1PR0701MB191453938CCDD842F97014F3DE640@HE1PR0701MB1914.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=srinivasa.rao.nalluri@ericsson.com;
x-originating-ip: [125.16.137.146]
x-ld-processed: 92e84ceb-fbfd-47ab-be52-080c6b87953f,ExtAddr
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB1914; 7:ZBBcr8fubHThsjDFdieaJy58+QnPlMlVZV1diGp4MI2XEnO0o/zjL6vVVgoebwY8iM/dOHdBAUSMh/aWiybPxoD5X10abIeUCr6KEBv2AtFKHvtxF4p1qMjswIRaS4yKAhdCMidTvvudKIWJ3jt8pCelXVB5CJavYRpwlmpk/q677yHf+hYfT/eoLfUvc83sk0/HsZ7q48PUyJUd2cXamwz565iOfSOQ7Ei/F9+hfZtQ3W8NDjFjdM8kK3PnKgBSwM0yM4RrCdCgdXJKC2A3iIovptk6uR0fOWGtFcElyEEJqXRfPiLr0QEsDNDR1wTwVuoGujxjbBv4NmWehEB+FfhtrfrIOigwYKZYbgg52j3wiWX3Hq0WY1NGjF/4pSwLx0XZSvDNyhsbLElgHd/5WjFnpxaCnLER3HWUt9s0CBgnSFGmLdPMbYE4jM2uDoSMSEltnq/D840f2nVZAdktJA==
x-forefront-antispam-report: SFV:SKI; SCL:-1SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(199003)(189002)(6306002)(189998001)(5630700001)(50986999)(54356999)(4001430100002)(101416001)(107886002)(97736004)(4326007)(25786008)(5660300001)(6436002)(606005)(7906003)(74316002)(7736002)(5640700003)(6916009)(7696004)(110136003)(2900100001)(77096006)(92566002)(6506006)(1730700003)(38730400001)(81156014)(81166006)(106356001)(105586002)(3660700001)(3280700002)(33656002)(55016002)(8676002)(2351001)(2501003)(2906002)(54906002)(99286003)(66066001)(122556002)(8936002)(19609705001)(102836003)(6116002)(9326002)(790700001)(450100001)(86362001)(3846002)(54896002)(68736007)(9686003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB1914; H:HE1PR0701MB1914.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
x-ms-office365-filtering-correlation-id: 0a6f2d62-7b85-4cf1-cdb3-08d4385d2156
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:HE1PR0701MB1914;
x-microsoft-antispam-prvs: <HE1PR0701MB19149D930B3330184FFD01F1DE640@HE1PR0701MB1914.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(192374486261705)(21748063052155)(21532816269658);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123564025)(20161123562025)(20161123555025)(20161123560025)(6072148); SRVR:HE1PR0701MB1914; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB1914;
x-forefront-prvs: 0182DBBB05
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0701MB191453938CCDD842F97014F3DE640HE1PR0701MB1914_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jan 2017 07:00:00.6631 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB1914
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPKsWRmVeSWpSXmKPExsUyM2K7q+43k+IIg+ZtPBZ3O1oYHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMe3iWcaCHZYV9+c2sjQwNhl1MXJySAiYSJx8s529i5GLQ0hg HaPE6RNLWSGc44wSjfs3MoM4LAK9zBKdjXdYIDIzmCSu//kJ1XOSUeJ76yFmkGFsAg4S06Y9 ZQOxRQRUJVYenMwOYjML7GOS+NhkBWILCxhLnF8wiR2ixkLi8+5pULaexPYDj8F6WQRUJL4c nsIEYvMKJEj8W/EMLM4oICbx/dQaJoiZ4hK3nsxngnhCQGLJnvPMELaoxMvH/1gh6lMlZh+/ ARVXknhyYyMjhG0jMaN7OthrEgJ9LBLHFnxmgUisYJPobpOBsH0llmx9xg5h+0tMe7wZys6X OH/uIZSdI9E76SnMICaJZXd7gS7lAHJkJHbtSwKpEQI6YvnaVkaI56Uk7l7phLJlJF7c2cs6 gVFjFpJ/IOx8iflLH7DOAvtfUOLkzCcsEHE9iRtTp7BB2NoSyxa+ZoawdSVm/DvEgiy+gJF9 FaNocWpxUm66kbFealFmcnFxfp5eXmrJJkZgsjm45bfqDsbLbxwPMQpwMCrx8H4ILooQYk0s K67MPcQowcGsJMLLalQcIcSbklhZlVqUH19UmpNafIhRmoNFSZzXbOX9cCGB9MSS1OzU1ILU IpgsEwenVAOjkhfvbp9khjLf8itmL6euf8JrMHPKsW6LzckfO/p+Pwy+KtOpp+ZaMPFtSNSc +fptBvukbcVcjzUU8sfLbtx/Q3etRePS/RPO1DwyeD3v4r6DH744bwjelbt5ydvMLVIPRR+W 8fSlLP6mlGyTZTjBUOr76t/puyw+uzC8Mv+eMFXlcNCUTQ/PK7EUZyQaajEXFScCAI/Ct0Yy AwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/OqCkjuHW4lFVNLz0WcNYqpO45QU>
Cc: Ari Keränen <ari.keranen@ericsson.com>, Srinivasa Rao Nalluri <srinivasa.rao.nalluri@ericsson.com>, Jan Melen <jan.melen@ericsson.com>, Jaime Jiménez <jaime.jimenez@ericsson.com>, Amit Gupta X <amit.x.gupta@ericsson.com>
Subject: [dhcwg] DHCP and DHCPv6 options for LWM2M services
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jan 2017 07:00:09 -0000

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.

https://www.ietf.org/internet-drafts/draft-nalluri-dhc-dhcpv6-lwm2m-bootstrap-options-01.txt

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

v2.23.0 | Report a Bug | By Email