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

Sheng Jiang <> Fri, 08 November 2013 18:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CE8A521E81CD for <>; Fri, 8 Nov 2013 10:01:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.563
X-Spam-Status: No, score=-6.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DzuyAhd2w7Zq for <>; Fri, 8 Nov 2013 10:01:34 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 038C121E8082 for <>; Fri, 8 Nov 2013 10:01:33 -0800 (PST)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id AXR57991; Fri, 08 Nov 2013 18:01:32 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 8 Nov 2013 18:01:25 +0000
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 8 Nov 2013 18:01:27 +0000
Received: from ([]) by ([]) with mapi id 14.03.0158.001; Sat, 9 Nov 2013 02:01:23 +0800
From: Sheng Jiang <>
To: Yusuke DOI <>
Thread-Topic: [dhcwg] New Version Notification for draft-jiang-dhc-stateless-reconfiguration-00.txt
Thread-Index: AQHOw9nQKCTG6gv4S0OORgUv/i3SN5nsBO9QgCrIX4CABQLdQA==
Date: Fri, 8 Nov 2013 18:01:22 +0000
Message-ID: <>
References: <> <>, <>
In-Reply-To: <>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-GB
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<>" <>
Subject: Re: [dhcwg] New Version Notification for draft-jiang-dhc-stateless-reconfiguration-00.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 08 Nov 2013 18:01:40 -0000

Hi, Yusuke,

Thanks for your use case. We will inlcude the abstract desciption into next version, which will include several suitable use cases.

Also thanks for your opinion on my designing questions. We are still in early state regarding to design the solution. We are open for all kinds of feedback.

Best regards,

From: Yusuke DOI []
Sent: 06 November 2013 5:25
To: Sheng Jiang
Cc: <>
Subject: Re: [dhcwg] New Version Notification for       draft-jiang-dhc-stateless-reconfiguration-00.txt

Dear Sheng, and WG members,

Let me describe the issue I've introduced on the meeting with regard to

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 <>