Re: [dhcwg] DHC WG charter

Ted Lemon <Ted.Lemon@nominum.com> Sat, 15 June 2002 03:59 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 XAA23679 for <dhcwg-archive@odin.ietf.org>; Fri, 14 Jun 2002 23:59:44 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id AAA23701 for dhcwg-archive@odin.ietf.org; Sat, 15 Jun 2002 00:00:22 -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 XAA23493; Fri, 14 Jun 2002 23:58:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA23467 for <dhcwg@optimus.ietf.org>; Fri, 14 Jun 2002 23:58:42 -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 XAA23641 for <dhcwg@ietf.org>; Fri, 14 Jun 2002 23:58:03 -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.3/8.6.11) with ESMTP id g5F3uCS28187; Fri, 14 Jun 2002 20:56:12 -0700 (PDT)
Received: from tongpanyi (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.12.2/8.6.11) with ESMTP id g5F3wcgF001276; Fri, 14 Jun 2002 22:58:38 -0500 (CDT)
Date: Fri, 14 Jun 2002 22:58:38 -0500
Subject: Re: [dhcwg] DHC WG charter
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v482)
Cc: dhcwg@ietf.org
To: rbhibbs@pacbell.net
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <JCELKJCFMDGAKJCIGGPNOEOKDNAA.rbhibbs@pacbell.net>
Message-Id: <2C054C5A-8014-11D6-9A23-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

> ...now my biases are showing....  after my experience with "stealth"
> implementations of private MIBs for DHCP and DNS servers, I'm not so sure
> that a bit of encouragement isn't needed....  although I agree that if a
> protocol spec is thought to be useful, implementations and interoperability
> testing will occur.

If the stealth implementations make their customers happy, where's the 
problem?   Many a fine protocol has emerged out of a stealth implementation.
    People seem to be willing to implement good standards, so if you see a 
lot of stealth implementations, it's probably because nobody proposed a 
standard, or nobody could agree on one.   In a situation like this, 
experimentation is good (as long as the experimenters don't patent their 
solution, anyway...)


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