IETF Logo Mail Archive

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

"Bernie Volz (volz)" <volz@cisco.com> Thu, 12 January 2017 14:08 UTC

Return-Path: <volz@cisco.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 466D31296A1 for <dhcwg@ietfa.amsl.com>; Thu, 12 Jan 2017 06:08:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level:
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 2oDJc9KJUSCc for <dhcwg@ietfa.amsl.com>; Thu, 12 Jan 2017 06:08:12 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 471A71296A0 for <dhcwg@ietf.org>; Thu, 12 Jan 2017 06:08:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12125; q=dns/txt; s=iport; t=1484230092; x=1485439692; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=SzHy69Heq5dBXY0h50+85i/WWT8qT/qv5bQ1/GF3PWE=; b=kdKKqqoq02opYb40n1YA8Nk4nYpQNe8zhgZXgXThcjhSGdpkW2sSWxQ3 ll1XTe9ovw419u85ybt2qbfGaj4Yyxca6KAUVWRPOAWyOvP252pQBMZYt nlxIWsbyL7mgtSm8cEoQJO25bKK67FCxTqpHosWR267/6Y3t3Yy+1qofd Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AfAQBdjXdY/5JdJa1dGQEBAQEBAQEBAQEBBwEBAQEBgnJKAQEBAQEfX4ENjVGiFIMcgg+CDYYiAoF+PxQBAgEBAQEBAQFjKIRqBi1MEAIBCEYyJQEBBAENDYh4smOKFQEBAQEBAQEBAQEBAQEBAQEBAQEBAR2LJoQwhXoFj12LTwGRTJBzkmMBHziBRBWEax+BX4hMgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.33,349,1477958400"; d="scan'208,217";a="193927296"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jan 2017 14:08:11 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v0CE8Bev017037 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 12 Jan 2017 14:08:11 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 12 Jan 2017 08:08:10 -0600
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Thu, 12 Jan 2017 08:08:10 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Srinivasa Rao Nalluri <srinivasa.rao.nalluri@ericsson.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHCP and DHCPv6 options for LWM2M services
Thread-Index: AdJqRXTE4zv4sumCQiCdFGjUYw4CPACloITQ
Date: Thu, 12 Jan 2017 14:08:10 +0000
Message-ID: <a1c983ca2e7b41f4a39973d4c4b6aa05@XCH-ALN-003.cisco.com>
References: <HE1PR0701MB191453938CCDD842F97014F3DE640@HE1PR0701MB1914.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0701MB191453938CCDD842F97014F3DE640@HE1PR0701MB1914.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.244.118]
Content-Type: multipart/alternative; boundary="_000_a1c983ca2e7b41f4a39973d4c4b6aa05XCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/ocHs7HgaXnazOzLUmlvEcP3hbC8>
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 14:08:14 -0000

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