Re: [dhcwg] New Version Notification for draft-jiang-dhc-stateless-reconfiguration-00.txt

Yusuke DOI <yusuke.doi@toshiba.co.jp> Tue, 05 November 2013 21:25 UTC

Return-Path: <yusuke.doi@toshiba.co.jp>
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 4E5AD11E8125 for <dhcwg@ietfa.amsl.com>; Tue, 5 Nov 2013 13:25:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.089
X-Spam-Level:
X-Spam-Status: No, score=-7.089 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cnL2Vcr2qnBr for <dhcwg@ietfa.amsl.com>; Tue, 5 Nov 2013 13:25:41 -0800 (PST)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id 8959321F9E26 for <dhcwg@ietf.org>; Tue, 5 Nov 2013 13:25:39 -0800 (PST)
Received: from tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp ([133.199.232.103]) by imx12.toshiba.co.jp with ESMTP id rA5LPc9B017733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dhcwg@ietf.org>; Wed, 6 Nov 2013 06:25:38 +0900 (JST)
Received: from tsbmgw-mgw01 (localhost [127.0.0.1]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id rA5LPbcQ031386 for <dhcwg@ietf.org>; Wed, 6 Nov 2013 06:25:37 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw01 (JAMES SMTP Server 2.3.1) with SMTP ID 242 for <dhcwg@ietf.org>; Wed, 6 Nov 2013 06:25:37 +0900 (JST)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id rA5LPbAZ031380 for <dhcwg@ietf.org>; Wed, 6 Nov 2013 06:25:37 +0900
Received: (from root@localhost) by arc11.toshiba.co.jp id rA5LPbsn008894 for dhcwg@ietf.org; Wed, 6 Nov 2013 06:25:37 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id GAA08893; Wed, 6 Nov 2013 06:25:37 +0900
Received: from mx12.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id rA5LPbKM007661 for <dhcwg@ietf.org>; Wed, 6 Nov 2013 06:25:37 +0900 (JST)
Received: from spiffy21.isl.rdc.toshiba.co.jp by toshiba.co.jp id rA5LPb0J004764; Wed, 6 Nov 2013 06:25:37 +0900 (JST)
Received: from [133.199.16.175] (ivpn-1-175.mobile.toshiba.co.jp [133.199.16.175]) by spiffy21.isl.rdc.toshiba.co.jp (Postfix) with ESMTPS id 525AB97D60; Wed, 6 Nov 2013 06:25:35 +0900 (JST)
Message-ID: <5279624D.9080306@toshiba.co.jp>
Date: Wed, 06 Nov 2013 06:25:33 +0900
From: Yusuke DOI <yusuke.doi@toshiba.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.2; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>
References: <20131008035221.3492.40090.idtracker@ietfa.amsl.com> <5D36713D8A4E7348A7E10DF7437A4B923AD4661C@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AD4661C@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] New Version Notification for draft-jiang-dhc-stateless-reconfiguration-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 05 Nov 2013 21:25:50 -0000

Dear Sheng, and WG members,

Let me describe the issue I've introduced on the meeting with regard to 
draft-jiang-dhc-stateless-reconfiguration-00.

Target system we expect is a wireless mesh network runs over 
802.15.4e/g. It contains 1000s of nodes and expects quite low traffic. 
There are some configuration parameters (example is MPL parameters -- 
e.g. draft-doi-roll-mpl-parameter-configuration). At most cases, we 
don't expect any update of configuration. However, we have to expect 
some instances of mesh networks could go beyond default parameter's 
assumption. For example, we need to tweak the configuration if we have a 
mesh network with too high/low density, too many e2e hops or have higher 
background traffic than expected, etc.

Hence, we need to have a way to update configuration of a network, but 
we don't expect frequent change.

Current choice we have in our mind is to use stateful DHCPv6. This 
decision is made just because we have no other choice to distribute and 
update network-wide configuration. However, stateful DHCPv6 may 
introduce following problems.

1) lease renewal traffic
2) update delay

Because a mesh network cannot transmit much traffic, I expect lease time 
more than a day or even for a week to reduce the traffic. This makes we 
need to wait weeks to propagate configuration update.

Here is my preference to the questions on the draft/ppt.

Question 1: b) seems to be simplest
Question 2: We prefer direct advertisement because mesh networks may not 
be able to accomodate traffic from 1000s of nodes to update their 
configuration within short period of time.
Question 3: no opinion
Question 4: If just update trigger is sent from the server, I believe 
the update window should be specified with a DHCPv6 option. The window 
size depends on network configuration and how important the update is.

Best Regards,

-- 
// Yusuke DOI <yusuke.doi@toshiba.co.jp>