IETF Logo Mail Archive

Re: [dhcwg] DHCP Option for CableLabs Client Configuration

Ted Lemon <Ted.Lemon@nominum.com> Thu, 08 August 2002 21:07 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26957 for <dhcwg-archive@odin.ietf.org>; Thu, 8 Aug 2002 17:07:03 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA00928 for dhcwg-archive@odin.ietf.org; Thu, 8 Aug 2002 17:08:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA00676; Thu, 8 Aug 2002 17:02:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15963 for <dhcwg@optimus.ietf.org>; Thu, 8 Aug 2002 12:47:27 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19084 for <dhcwg@ietf.org>; Thu, 8 Aug 2002 12:46:11 -0400 (EDT)
Received: from green.bisbee.fugue.com (dsl-64-193-175-153.telocity.com [64.193.175.153]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id g78GkWv19832; Thu, 8 Aug 2002 11:46:32 -0500 (CDT)
Received: from tongpanyi (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.12.2/8.6.11) with ESMTP id g78Gl8Be000322; Thu, 8 Aug 2002 11:47:08 -0500 (CDT)
Date: Thu, 08 Aug 2002 11:47:07 -0500
Subject: Re: [dhcwg] DHCP Option for CableLabs Client Configuration
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v482)
Cc: Matt Osman <M.Osman@cablelabs.com>, pgrossma@cisco.com, nrussell@cisco.com, dhcwg@ietf.org, 'Ralph Droms' <rdroms@cisco.com>, "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>, Thomas Narten <narten@us.ibm.com>, Paul Duffy <paduffy@cisco.com>, Josh Littlefield <joshl@cisco.com>, "Woundy, Richard" <RWoundy@broadband.att.com>
To: Erik Nordmark <Erik.Nordmark@sun.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <Roam.SIMC.2.0.6.1028711045.22189.nordmark@bebop.france>
Message-Id: <79FE7C86-AAEE-11D6-8B54-00039367340A@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit

> There is in theory potential interoperability issues both for DHCP and DNS.
> DHCP: will things operate correctly if the MTA receives a good ol' DNS
> name server option instead of this suboption? If not you either get all
> the DHCP servers on the planet to implement the cablelabs option or you 
> could
> end up with interoperability problems.

It is always a risk that a DHCP server administrator will configure the 
DHCP server incorrectly.   This is an example of an incorrect configuration.
    There is nothing that you can do in the protocol to prevent an incorrect 
configuration.   For example, if I configure my DNS server to do TSIG 
updates, but I put the wrong TSIG key data on the client, the update 
inexplicably doesn't work.   As the administrator, I just have to figure 
that out and fix it.   The protocol can't help me - it has no way to report 
that the signature didn't verify, because an invalid signature means the 
packet should be tossed.   Is this a bug in the protocol?   (I don't think 
so!)



_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email