Re: [dhcwg] Please review draft-ietf-pcp-dhcp, particularly section 5.

Simon Perreault <simon.perreault@viagenie.ca> Wed, 19 March 2014 17:55 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 293D71A07CC for <dhcwg@ietfa.amsl.com>; Wed, 19 Mar 2014 10:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vi7_LGjkk1a2 for <dhcwg@ietfa.amsl.com>; Wed, 19 Mar 2014 10:55:53 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 033281A07D1 for <dhcwg@ietf.org>; Wed, 19 Mar 2014 10:55:51 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:f981:e226:281f:c92d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 38DD44037C; Wed, 19 Mar 2014 13:55:42 -0400 (EDT)
Message-ID: <5329DA1D.2010306@viagenie.ca>
Date: Wed, 19 Mar 2014 13:55:41 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
References: <94C682931C08B048B7A8645303FDC9F36F51A2DB17@PUEXCB1B.nanterre.francetelecom.fr> <C7964664-C302-4ABE-9CAC-1AD5D9048699@cisco.com> <489D13FBFA9B3E41812EA89F188F018E1AF1C1CA@xmb-rcd-x04.cisco.com> <5329B584.1090404@viagenie.ca> <CBE2A263-A6B8-4B46-9454-6F63731DE0DC@nominum.com> <5329D758.6050404@viagenie.ca> <46BCE74E-D2DA-4E8B-8007-D987FFE04874@nominum.com>
In-Reply-To: <46BCE74E-D2DA-4E8B-8007-D987FFE04874@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/M6My3B0ID9lVty7OkB6E0wLwuQM
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Please review draft-ietf-pcp-dhcp, particularly section 5.
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Mar 2014 17:55:55 -0000

Le 2014-03-19 13:50, Ted Lemon a écrit :
> On Mar 19, 2014, at 1:43 PM, Simon Perreault <simon.perreault@viagenie.ca>; wrote:
>> Sure. As I said, just a data point. Everything else being equal, it
>> would be nice if no programming was necessary.
> 
> Given that no standard currently recommends similar behavior, it seems like a bad idea to define a new DHCP feature just because it happens to work in some code base (if, indeed, it does).   It would be better to decide what the right design is and make the minor code changes to support it if necessary.

Fully agreed.

I'll try to be even clearer: *everything else being equal*, it's nice
when no programming is needed. If nobody can come up with a clever
solution that allows us to have our cake and eat it too, then that's the
end of the story. I'm not asking that we restrict ourselves to what is
doable without programming.

It was just a data point... *sigh*

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca