IETF Logo Mail Archive

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

Srinivasa Rao Nalluri <srinivasa.rao.nalluri@ericsson.com> Thu, 12 January 2017 16:04 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 13CC2129485 for <dhcwg@ietfa.amsl.com>; Thu, 12 Jan 2017 08:04:46 -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 G1yIjvDgWIfT for <dhcwg@ietfa.amsl.com>; Thu, 12 Jan 2017 08:04:39 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 997741294C4 for <dhcwg@ietf.org>; Thu, 12 Jan 2017 08:04:38 -0800 (PST)
X-AuditID: c1b4fb3a-f21fe70000002085-ac-5877a913e2ae
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by (Symantec Mail Security) with SMTP id B6.27.08325.319A7785; Thu, 12 Jan 2017 17:04:36 +0100 (CET)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.87) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 12 Jan 2017 17:05:21 +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=aoyCZ2eIhaovidj0KYxKwi8EIChErBl1naZ2F/o/Azk=; b=mzt8clE68/UC3GBfjZVhfE5aoKeHzB+7uW84MridebJBHvQUN2VM8fU68czlBOkN38ie1oeFh5Zdy7d0aBi+zPJAP28Itnb764/OMxUPFL4v7Crl34uOZSeVtSWyCyncs/XxBjG2nfyqFnZdxki8mOaBI0uBmRLcmT/36hjcRtM=
Received: from HE1PR0701MB1914.eurprd07.prod.outlook.com (10.167.189.18) by AM2PR07MB0978.eurprd07.prod.outlook.com (10.162.37.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.845.6; Thu, 12 Jan 2017 16:04:34 +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.0845.012; Thu, 12 Jan 2017 16:04:33 +0000
From: Srinivasa Rao Nalluri <srinivasa.rao.nalluri@ericsson.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHCP and DHCPv6 options for LWM2M services
Thread-Index: AdJqRXTE4zv4sumCQiCdFGjUYw4CPACloITQAAQvOOA=
Date: Thu, 12 Jan 2017 16:04:32 +0000
Message-ID: <HE1PR0701MB19145E70B77D371941A6AE2FDE790@HE1PR0701MB1914.eurprd07.prod.outlook.com>
References: <HE1PR0701MB191453938CCDD842F97014F3DE640@HE1PR0701MB1914.eurprd07.prod.outlook.com> <a1c983ca2e7b41f4a39973d4c4b6aa05@XCH-ALN-003.cisco.com>
In-Reply-To: <a1c983ca2e7b41f4a39973d4c4b6aa05@XCH-ALN-003.cisco.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: [203.212.244.198]
x-ld-processed: 92e84ceb-fbfd-47ab-be52-080c6b87953f,ExtAddr
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0978; 7:n15aUWpA3+2D3+JCaZIlokZYD31F0ptC3uUBBKKRqKBOVB37uQ0ckU0uUAG21m8lo/qrsvxDgs3tzJO2NZfyafHCux7YBrdj5LVCqfvjbk0nhP2BPBa8JaZBqQ4ME5IOZxiBuEZFjI+e24X4D+4gHsFce88eSoEA8ewQzf5vilzTqShhjTr5vnSb+phNXyfeARPQQ39FfPaZroeHZykqX+8jA1crIuW+TViC5iNXEr7sHHSRmMri77x6q5JglBVNncm4ZxdYIt0g6Mbu1/vw+pnRhHqJoDAfy55HRFY9TdYLmLx8CPZj4oHmE9HUS1MDQVJt8KO0Pw/B3MxbYBETZ5tj6LGMToMgg82h5mKb9NJNrPGtWa16X/DJ9IvgptlyfQca62vVqfz2FxJfKyIbwW91pKWPBA0zY4GfFNVwCkNNx+efBes3wOsPZK9ePxvM7QtywEKLPLpEh5LTcCmndA==
x-forefront-antispam-report: SFV:SKI; SCL:-1SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(199003)(189002)(377454003)(6116002)(2950100002)(92566002)(19609705001)(6506006)(66066001)(6436002)(97736004)(54906002)(229853002)(99286003)(33656002)(2906002)(55016002)(189998001)(107886002)(5001770100001)(86362001)(38730400001)(25786008)(77096006)(3846002)(102836003)(7696004)(5660300001)(790700001)(2501003)(106356001)(2900100001)(3280700002)(54356999)(76176999)(6306002)(54896002)(9686003)(68736007)(122556002)(3660700001)(74316002)(81166006)(105586002)(4001430100002)(8676002)(101416001)(7736002)(8936002)(4326007)(50986999)(81156014); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0978; H:HE1PR0701MB1914.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
x-ms-office365-filtering-correlation-id: e915cb2f-b6ad-4f07-26e0-08d43b04b30f
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM2PR07MB0978;
x-microsoft-antispam-prvs: <AM2PR07MB097824F476540D5934D46F28DE790@AM2PR07MB0978.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041248)(20161123562025)(20161123564025)(20161123555025)(20161123560025)(20161123558021)(6072148); SRVR:AM2PR07MB0978; BCL:0; PCL:0; RULEID:; SRVR:AM2PR07MB0978;
x-forefront-prvs: 018577E36E
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_HE1PR0701MB19145E70B77D371941A6AE2FDE790HE1PR0701MB1914_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jan 2017 16:04:33.0792 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0978
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SbUhTYRTHee69m1dx8LQ0D6Z9mBSlaKaS06T0Q+CHLKPIYYUuvamp03Zt pvjByLBMw2jqpoQGNpnVoswyt0xX4kviW/mSqRlaYSMhtBcxR+4+Bn77nf/5n+e88LC01Cjy ZNNUOZxapcyQiV0YvWK1wN/NmKsIvHlNLp+6WoTkDbpdkVS0duWRKLq+fpmKpeJdIpK5jDQN p969P9EldeW9hcpuUVwc1oUUIltMCXJmAYeA6ZKBLkEurBQ/RFBl/8KQoBtB558xkSNgcBkN TSMGMclUUfDq3aCIBL0Imi7raMdjYhwJlZWfxQ52w4dgssMmVNC4H4G1u10wbcahYDJPM8Qk h0VzpRPhcHj+okLwMHg72EftIgdLcCL86JlZ71aDwPamT+jgjA/CUEuXUIDwFvjde59yMI09 YGKuliLrYai3DNCE3WF+ljyKMAc1XePrug887WtY90eA7nqVcA7ApQxM9JgpEhSJoeaXBRFX DHwYeLa2AiuwZTaWyOmgm34tIvJJ+DuSQkqrKdC2zq4384LbpW3CENK1IRoeXEHlyLd6w9yE s+D7gllcLRxgE/To5xiiB8B4hVZM2A8Md2w0YX/Q2a3MRr0OOTUid57j+cyUoKAATp2WxPNZ qgAVl/MYrX2gjicr4S2o42uUFWEWyVwl2dEahVSk1PB5mVYELC1zk8TdzVVIJcnKvHxOnZWg vpDB8Va0lWVkHpK9xo9xUpyizOHSOS6bU//PUqyzZyFSjuuHXBuL9wV2exXXne7fcWymqCas YKqs4ps8/0TUykjw8synM6Fce4we++7M0yyrvdyWBuZMXGJSQtMCO1d+trVruOjGvcPzpubg A9oxv6Co2s42Y9jS6vlzzUPb3h7NiH2pih9lJ4/Pp1sNRq1fCx4+Yh/0PhW+6OP9847qlozh U5V7fGk1r/wHL6fzvjwDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/Ofc7KHmZrHVQeqVtJ9jw69St4wc>
Cc: Amit Gupta X <amit.x.gupta@ericsson.com>, Jan Melen <jan.melen@ericsson.com>, Ari Keränen <ari.keranen@ericsson.com>, Jaime Jiménez <jaime.jimenez@ericsson.com>
Subject: Re: [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: Thu, 12 Jan 2017 16:04:46 -0000

Hi Bernie Volz,

Thanks for your review and comments.
#1 In genera in other documents 'DHCP' is used to indicate DHCP for IPv4 networks and 'DHCPv6' is used to indicate DHCP for IPv6 networks. Anyhow what you said makes sense  and looks clear way. I will consider for next version.

#2 I will consider this for next version.

Thanks & Regards
Srinivas

From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Thursday, January 12, 2017 7:38 PM
To: Srinivasa Rao Nalluri; dhcwg@ietf.org
Cc: Ari Keränen; Jan Melen; Jaime Jiménez; Amit Gupta X
Subject: RE: DHCP and DHCPv6 options for LWM2M services

Hi:

A couple of (I think) additional comments on this draft:


1.       It be best to use DHCPv4 and DHCPv6 (and use DHCP for when you are specifically referring to both)? For example, it helps to be clear that an option is a v4 vs v6 option.

2.       For the DHCPv4 , you don't need the sequence number in the OPTION_LWM2M_SERVER_CERTIFICATE option and much of the text below. DHCPv4 already supports LONG options (more than 255 bytes of data) - see RFC 3396 - Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4). You just need to say that this option uses this encoding.

   Maximum possible value of DHCP "option-len" is 255.  LWM2M-server-
   certificate MAY be of length more than 255.  To accommodate larger
   certificate, it SHOULD be possible to include multiple
   OPTION_LWM2M_SERVER_CERTIFICATE options in same DHCP message.  DHCP
   server SHOULD be capable of including multiple
   OPTION_LWM2M_SERVER_CERTIFICATE options in same message.
   Certificates larger than 255 byte SHOULD be fragmented and adjusted
   in minimum possible number of OPTION_LWM2M_SERVER_CERTIFICATE
   options.  Each OPTION_LWM2M_SERVER_CERTIFICATE option is tagged with
   a sequence number which can be used by DHCP client to reassemble
   received certificate


-          Bernie

v2.23.0 | Report a Bug | By Email