Re: [dhcwg] What sorts of services does DHCP configure?

Sheng Jiang <> Fri, 18 October 2013 01:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 19E1C11E81B1 for <>; Thu, 17 Oct 2013 18:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.576
X-Spam-Status: No, score=-6.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2BLMW9rmlRP8 for <>; Thu, 17 Oct 2013 18:57:57 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5C03311E813D for <>; Thu, 17 Oct 2013 18:57:56 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id AWX23620; Fri, 18 Oct 2013 01:57:46 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 18 Oct 2013 02:56:44 +0100
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 18 Oct 2013 02:57:41 +0100
Received: from ([]) by ([]) with mapi id 14.03.0146.000; Fri, 18 Oct 2013 09:57:37 +0800
From: Sheng Jiang <>
To: Robert Elz <kre@munnari.OZ.AU>
Thread-Topic: [dhcwg] What sorts of services does DHCP configure?
Thread-Index: AQHOynEUQEQ991LaX0ejQZk7nFFTAJn22XWAgAE1vTD//6m3gIAAihww//98xoCAAKEVgIAABtkAgAFEW4A=
Date: Fri, 18 Oct 2013 01:57:37 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: " WG" <>, Ted Lemon <>, "Bernie Volz \(volz\)" <>
Subject: Re: [dhcwg] What sorts of services does DHCP configure?
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, 18 Oct 2013 01:58:04 -0000

>Sheng>  | Why DHC WG cannot say no to what should not be in DHC?
>Would you ask the same question if it were the TCP working group attempting
>to stop some application protocol because the TCP people didn't like it?

The question is different here. The application protocol use TCP as a transparent deliver tool. They does not request anything from TCP resource. The DHC WG cannot stop people to use DHC protocol as a platform. But the DHC WG should have the right to say: you can do whatever you want over DHCP platform for any purposes, but you CANNOT get official DHCP Option code assigned by IANA if that does not approved by DHC Directorate. In another word, DHC Option code is a resource, controlled by DHC Directorate and should only be assigned to these correct usages.


>The DHCP working group's job is to make DHCP work - improving as much
>as possible the efficiency, reliability, and security - as with any other
>It isn't to dictate how others use the result.   If some other WG has a
>use for some data, and having that deliver delivered by DHCP looks to be
>the best way (to them) then provided the idea survives IETF last call,
>it really is no-one else's business.
>Of course this WG (and anyone else) can suggest alternatives, or describe
>problems, and suggest better ways - but no-one gets (unilaterally) to
>impose road blocks.    Ted was right in what he said - if the proposal in
>question isn't a good idea, by all means say so, but don't start believing
>that this group has any right to tell any other what they can or cannot do.