Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-ddns-resolution-09.txt>

Ted Lemon <Ted.Lemon@nominum.com> Tue, 12 July 2005 22:22 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsT90-0001K8-Sg; Tue, 12 Jul 2005 18:22:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsT8y-0001GA-Oq for dhcwg@megatron.ietf.org; Tue, 12 Jul 2005 18:22:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24875 for <dhcwg@ietf.org>; Tue, 12 Jul 2005 18:22:22 -0400 (EDT)
Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsTbE-0007mo-J3 for dhcwg@ietf.org; Tue, 12 Jul 2005 18:51:38 -0400
Received: from [10.222.34.112] (m975f36d0.tmodns.net [208.54.95.151]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client did not present a certificate) by shell-ng.nominum.com (Postfix) with ESMTP id 432D756906; Tue, 12 Jul 2005 15:21:56 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
In-Reply-To: <20050712221024.GF27743@isc.org>
References: <1120944721.12354.64.camel@localhost.localdomain> <8737CA55-609B-44D9-80AF-DCF4494A1C56@nominum.com> <20050712221024.GF27743@isc.org>
Mime-Version: 1.0 (Apple Message framework v728)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <A8160191-E1F5-4AE3-9378-067F50050720@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-ddns-resolution-09.txt>
Date: Tue, 12 Jul 2005 17:21:50 -0500
To: "David W. Hankins" <David_Hankins@isc.org>
X-Mailer: Apple Mail (2.728)
X-Spam-Score: 2.9 (++)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

On Jul 12, 2005, at 5:10 PM, David W. Hankins wrote:
> Since the first step the document outlines is the query, I think most
> under-educated implementors would follow it.

Anytime you say "just do it however you like" in a protocol  
specification, you can bank on the fact that someone is going to do  
it completely wrong.   The whole point of specifying a protocol is  
not so that implementors can pick and choose what they want to do,  
but so that implementors have a specific way of doing things that  
will definitely produce the right result.   Implementors are always  
free to not follow the specification, and as long as what they do  
works, that's fine, but if there's a need for a protocol  
specification, the protocol specification should specify a  
protocol.   So while it's always true the implementations MAY not  
follow the protocol, there's no need to encourage them.


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