Re: [dhcwg] DHCP Option for CableLabs Client Configuration

Josh Littlefield <joshl@cisco.com> Thu, 01 August 2002 20:40 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 QAA14337 for <dhcwg-archive@odin.ietf.org>; Thu, 1 Aug 2002 16:40:44 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id QAA20953 for dhcwg-archive@odin.ietf.org; Thu, 1 Aug 2002 16:41:53 -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 QAA19561; Thu, 1 Aug 2002 16:13:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19539 for <dhcwg@optimus.ietf.org>; Thu, 1 Aug 2002 16:13:06 -0400 (EDT)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13517 for <dhcwg@ietf.org>; Thu, 1 Aug 2002 16:11:56 -0400 (EDT)
Received: from cisco.com (dhcp-128-107-208-82.cisco.com [128.107.208.82]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id QAA19935; Thu, 1 Aug 2002 16:09:29 -0400 (EDT)
Message-ID: <3D499578.4020608@cisco.com>
Date: Thu, 01 Aug 2002 16:09:28 -0400
From: Josh Littlefield <joshl@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@sun.com>
CC: Paul Duffy <paduffy@cisco.com>, Thomas Narten <narten@us.ibm.com>, "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>, 'Ralph Droms' <rdroms@cisco.com>, dhcwg@ietf.org, nrussell@cisco.com, pgrossma@cisco.com, Matt Osman <M.Osman@cablelabs.com>
Subject: Re: [dhcwg] DHCP Option for CableLabs Client Configuration
References: <Roam.SIMC.2.0.6.1028221934.11118.nordmark@bebop.france>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
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

Erik Nordmark wrote:
>>1.  A primary use case is for testing/lab/trial deployments.  The only way 
>>to configure an MTA (a headless, embedded device) for a non standard port 
>>number would be via the CCC sub-option 4/5 mechanism.
> 
> 
> That seems like an argument for perhaps an experimental RFC, but
> as I understand it the intent is to make this specification a proposed
> standard.
> 

Couldn't this also be a reasonable operational feature?  The use of DNS in 
PacketCable (as specified by these sub-options) is quite restricted.  Using 
non-standard ports may, for example, allow deployment of a specific DNS 
server for PacketCable on the same device as a general nameserver.  Or it 
might just allow extra confidence that the queried server is, in fact, not a 
general purpose Internet DNS server, but a PacketCable specific one.

If CableLabs participants (including operators) have felt the desire to 
deploy these DNS servers on non-standard ports, why shouldn't they be able 
to do that?  Why shouldn't the DHCP configuration info which is specific to 
PakcetCable (or similar CableLabs standards) support that?


-- 
=====================================================================
Josh Littlefield                                  Cisco Systems, Inc.
joshl@cisco.com                                      250 Apollo Drive
tel: 978-497-8378  fax: same               Chelmsford, MA  01824-3627


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